Fourth assignment-- Demand Analysis

[Jcandc]

In order not to miss any homework details, here’s a checklist for students to quickly review.

• Demand Analysis Assignment

  • (1) 1 blog essay (including the assignment directory, and checking the scoring points);

  • (2) 1 copy of the requirements specification (Word electronic version) (upload to gitcode or CSDN, give a link in the blog, it is recommended to save it as a PDF for upload);

  • (3) 1 demand analysis report PPT (classroom narrative) (upload to gitcode or CSDN, give a link in the blog, it is recommended to save it as a PDF for upload);

  • (4) 1 demand analysis review form (Tencent shared document)

Deadline

• The deadline for this assignment is November 03, 2023, at 23:59. Blog review takes time, so please publish your blog in advance.

1. Assignment Content

• Scoring Rules for This Assignment
  • Total score = Presentation Score + Blog Score + Document Score
  • Presentation Score (consistent scoring rules for both presentations) = Total score given by other groups [e.g., Group 1 gives 80, Group 2 gives 90, so this item = 80 + 90] / (Total number of groups - 1) * 0.25 + Total score given by teaching assistants / (Number of teaching assistants) * 0.35 + Total score given by the teacher / (Number of teachers) * 0.40

Blog Content

• 1. Describe the team’s division of labor and the proportion of work for each team member. Please use the following markdown for the contribution table.

Student ID	Task Description	Contribution

• 1. Provide “Requirements Specification” as an attachment to the essay.

Requirements:

• 1. Refer to the national standard text of “Software Requirements Specification” to write the software requirements specification for the corresponding project.
  • In addition to meeting the requirements of the specification text in form, the overall content must focus on the essence of the project, and ensure that the project to be developed is as clear, complete and accurate as possible.
  • It is described in a hierarchical form. As the “layer” goes deeper, the details of the description become more specific.
  • Use consistent graphic symbols and text to describe content.
  • All abbreviations must be defined in advance.
  • Format: There needs to be a table of contents, the word layout style is standardized and beautiful, with pictures and texts, the entire document has a unified style, pay attention to fonts and line spacing, etc.
  • Put yourself in the reader’s shoes - if someone who is unfamiliar with the software project can read this document, can they fully understand what the software is supposed to do?
  • Visit real users of software projects to ensure that the software truly reflects the needs of users and lays the foundation for the final usability of the software.
• 1. Clarify the team organization method, member division of labor and rough schedule arrangement. It is necessary to describe the specific division of labor of each member and the workload proportion of the entire document task.
• 1. To strengthen the division of labor and collaboration among team members, it is necessary to describe how members collaborate.
• 1. Checklist: Introduction, user scenarios, class diagrams, functional descriptions, acceptance verification standards, document charts, text, and styles are unified and in compliance with specifications
• 1. Each group submits its own simple review form, including:

  • Group number, project name, student IDs of all group members, and the content being reviewed;

  • Grading for each group (percentage);

  • Grading reasons, including format, content, PPT, presentation, strengths, issues (at least 3 points), suggestions, etc. (Respect other groups, give fair and honest assessments, and ensure that the scores accurately reflect the quality of the report, avoiding uniformly high or low scores);

  • Customized table (Tencent shared document).

2. Assignment Evaluation Items and Evaluation Rules

Total score for this assignment: 100 points

• (20 points) Blog Writing [Covered Course Objective 7]

  • (5 points) Correctly provide links to software requirements specifications and requirements analysis PPT links

  • (5 points) Blog formatting using markdown.

  • (4 points) Analysis of possible key points and challenges during the assignment.

  • (6 points) Division of labor among team members and the proportion of their contributions to the assignment.

• (16 points) To strengthen the division of labor and collaboration among team members, it is necessary to describe the members’ collaboration methods in the blog. [Covering Course Objective 6]

• (32 points) Writing Software Requirements Specification [Covering Course Objective 2]

  • The process description specification details the design ideas, problems encountered and solutions to the implementation process.

  • (2’) Introduction

  • (8’) User scenario

  • (8’) Class diagram

  • (8’) Interface prototype

  • (3’) Function description

  • (3’) Acceptance verification standards

• (12 points) Refer to the national standard text of the “Software Requirements Specification” to write the software requirements specification for the corresponding project. [Covering Course Objective 5]

• (20 points) Presentation Score

  • (8 points) [Covering Course Objective 2]

    • (2 points) Purpose, significance and background of project development.
    • (6 points) Content of project research and development (class diagram)

  • (4 points) [Covering Course Objective 6]

    • (4 points) Execution of the team’s plan during the process, member division of labor, and workload proportion.

  • (8 points) [Covering Course Objective 5]

    • (4 points) PPT presentation.

    • (4 points) Report.

3. Rules & Formats

1. To facilitate reading and assistant grading, please provide a blog table of contents at the beginning of the blog as content index.

Make sure to include the following major headings, or similar meanings are acceptable, and you can personalize your own headings:

• Team Division of Labor
• Software Requirements Specification

2. For other schools’ teachers or assistants to understand the course situation, please add format descriptions at the beginning of the assignment:

This assignment belongs to which course	< Class Link >
Where this assignment is required	< Assignment Requirements Link >
Team name
The goal of this assignment	< Specific aspects >
Other references	…

3. Submission Rules

• The blog is submitted based on the submission time on the class assignment page; files to be submitted are based on the submission time on Gitcode;
• Submit before the deadline, and the score is the actual score;
  • If the post is published and under review (the post shows 404), you can submit the link to the assignment page before the deadline and then wait for approval.
  • No late submissions will be accepted due to upload failures, network issues, or other reasons.
• Late Submission: Submitting within two days after the deadline is considered a late submission, and the score is the actual score * 50%; writing but forgetting to submit the assignment and late submissions are penalized equally.
• Missed Deadline: Failing to submit the blog within two days after the deadline is considered a missed assignment, and the score is 0.
• Assignment Plagiarism: When the teaching assistant finds that two blogs have text/images/code that are too similar, both blogs are considered plagiarized, and both receive a score of -100% (note that this is a negative score!).
• Forgery of Submission: Although the assignment blog has not been completed, submitting it to occupy a place is considered a forged submission, and the score is 0.
  Note: For assignments submitted in advance, if you can actively respond to teaching assistant and teacher feedback and make corresponding revisions before the deadline, these improvements will be taken into account in the subsequent grading. Early preparation has many advantages.

4. Questions and Clarifications

If there are unclear aspects of the assignment or if you don’t understand something, you can ask in the QQ or WeChat group.

Appendix “Demand Rules Specification” Reference

Table of contents
1 Introduction
  1.1Purpose of writing
  1.2Project background
  1.3References
2.Overall description
  2.1 Objectives
   2.1.1 Development intention
   2.1.2Application goals and scope
   2.1.3 Product Prospects
3. Specific requirements
  3.1 Class Diagram
  3.2 Properties
  3.2.1 Availability
  3.2.2 Security
4. Interface prototype
5. Function description and acceptance verification standards
 5.1Detailed function description
5.2 Input and output format
 5.3 Interface Acceptance Criteria
 5.4 Functional Acceptance Criteria

Reference example

Introduction

1.1 Purpose of writing
 The function of the project is to implement DES_RSA hybrid encryption. For our team, it is to improve Java programming capabilities, and then combine it with cryptography knowledge to lay a solid foundation for future professional learning. It is also for potential ordinary users to implement daily file encryption.

1.2 Project background

Software name: DES_RSA hybrid encryptor

Project task proposer: Teacher Lou

-Project developer: AWN team

1.3 References
Teacher Registration System Requirements Specification
Buy together Required Specifications

2.General description
2.1 Goals
2.1.1 Development intention
Use UI technology to make the complex DES_RSA hybrid encryption file technology into an interface, and realize file encryption through simple buttons.

2.1.2 Application goals and scope
This system is aimed at all students who love passwords and implements simple txt file encryption.

2.1.3 Product prospects
The function of the system just now is relatively simple, but the big framework has been completed. We look forward to enriching the functions of the system after learning more knowledge in the future, and the product prospects are good.

1. Specific requirements
   3.1 Class diagram
   3.2.1 Availability
   (1) Easy to operate and understand, the interface design is simple and easy to use.
   (2) Fault tolerance: The system has certain fault tolerance and anti-interference capabilities. When the user inputs a format error, the system will prompt and can input again.

3.2.1 Security
Keys, ciphertext and other files exported during program running are stored in a secure folder.

4 interface prototype
It’s not implemented yet, it will be added later.

1. Function description and acceptance verification standards
   5.1 Specific function description
   You can import plain text to be encrypted from your computer
   In the RSA encryption stage, the number of digits of prime numbers p and q (default 200 bits) can also be selected, and p and q can be exported.
   The public key e and private key d can be exported
   Decrypted files can be exported

5.2 Input and output format
The imported plain text file format is .txt
The exported plain text file format is .txt

5.3 Interface acceptance criteria
User encryption interface
Input the file. There is a display box in the middle to display the file name of the file to be encrypted; there is an import file button on the right for importing plain text and an encryption button.
The encryption module has a prompt on the far right of the selection box for the number of digits of prime numbers p and q (the number of digits for p and q is preferably more than 200). There is a button in the middle to generate a prime number p and export a prime number p, and there is a corresponding display box to generate a prime number q and export it. The button of prime number q has a corresponding display box. There is a button to generate prime number pairs, and there are buttons to export modulo n, public key e, and private key d below the interface. Finally, there is a DES key export button and a corresponding display box.
Output file There is a display box in the middle to display the file name of the encrypted file; there is an export file button on the right for exporting ciphertext.
User decryption interface
Input file There is a display box in the middle to display the file name of the file to be decrypted; there is an import file button on the right for importing ciphertext.
The decryption module has an input box for entering the password (DES public key file)
Output file There is a display box in the middle to display the file name of the successfully decrypted file; there is an export file button on the right for exporting plain text.
5.4 Functional acceptance criteria
Implement all functions introduced in the interface.