[go: up one dir, main page]

0% found this document useful (0 votes)
47 views2 pages

APCS 300/CTT 502 - Introduction To Software Engineering: Project Assignment 2 (PA2)

This document outlines Project Assignment 2 for an introductory software engineering course. It includes 5 required documents for submission: a revised project plan, detailed vision document, use-case model diagram(s), use-case specification document detailing each use-case, and a weekly report. Students must compile the documents into a zip file named after their group for grading based on criteria such as English writing quality, formatting, completeness, and matching requirements in the vision document.

Uploaded by

NgọcĐức
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
47 views2 pages

APCS 300/CTT 502 - Introduction To Software Engineering: Project Assignment 2 (PA2)

This document outlines Project Assignment 2 for an introductory software engineering course. It includes 5 required documents for submission: a revised project plan, detailed vision document, use-case model diagram(s), use-case specification document detailing each use-case, and a weekly report. Students must compile the documents into a zip file named after their group for grading based on criteria such as English writing quality, formatting, completeness, and matching requirements in the vision document.

Uploaded by

NgọcĐức
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

APCS 300/CTT 502 - Introduction to Software Engineering

Project Assignment 2 (PA2)


Due date:
Total points​:​ 70 points

This is a project assignment which will be submitted by each team.


You have the following documents to be done and submitted.

a – Revised project plan – 2nd submission (10 points)


Based on the comments in PA1 you need to update your project plan to fix the issues found by
TA’s and make it clearer and more detailed. Also, detail the schedule and other sections with
more information that you have now.

b – Detailed vision document – 2nd submission (10 points)


Detail product functional and non-functional requirements, alternatives and competitors, user
environments. Your team can take a look at the TA’s comments in PA1 as a suggestion.

Similar to the project plan, you are required to fully complete the document then submitting it
again.

c – Use-case model (10 points)


Based on the requirements documented in the vision document, model use-cases of the system
in forms of use-case diagrams (one or several diagrams). Each diagram includes use-cases,
actors and relationships among them. You can use StarUML, Visio or another tool to design the
use-case diagram. Place the diagram in the use-case specification document (see below).

d – Use-case specification (35 points)


Detail each use-case in the use-case diagram by filling the use-case specification document,
focusing on name, basic flow, alternative flows, pre-conditions, and post-conditions. Use the
template for the use-case specification document provided along with this asignment.

e – Weekly report (5 points)


Prepare weekly reports for the weeks doing this assignment. Fill out the template with all
information required.

Submission Rules​:
You must copy all documents to the directory named ​PA2-Group[GroupId]​ and compressed the
whole directory to zip/rar file
For example: ​PA1-Group01.zip
Grading Criteria:

The assignment will be graded according to how well your team prepares the required
documents using the information your team has at this time. Criteria include:

● English writing: easy to understand, few errors.


● Well formatted texts, diagrams, charts.
● Level of completeness of the documents, based on the information available at this time.
● Each use-case must have a main flow.
● Use-case diagrams must include key use-cases that match the functional requirements
documented in the vision document.

- END -

You might also like