aadsdaadsasd

0 comments

You just need to create a UML class that contains the definition of attributes and the definition of operations. You should describe variables too. I already attached the project.

The second deliverable in the course project (after the requirement specification) is the software design specification that describes the software organization and development plan. In contrast to the software requirements specification that is intended to be read by the client, the software design document is meant for the developers that implement the software components and later maintain the software product. Specifically, the software design specification document should describe the overall software architecture and implementation, at a level of detail similar to a UML Class Diagram. The classes, data structures, together with all major functions and their parameters should be specified.

Some software system descriptions are provided. You are also free to propose your own software system. You will work on the system you select for this assignment for the remainder of the semester.

Submissions will be done through your project group github page. Push your software design specification as a pdf or txt file to your group project repository, and submit the link to the file. Only one submission per group is required.

The document submitted by your team should include the following content:

Title page

  • Software title
  • Team members

System Description

  • Brief overview of system

Software Architecture Overview

  • Architectural diagram of all major components
  • Description of classes
  • Description of attributes
  • Description of operations

* descriptions should be detailed and specify datatypes, function interfaces, parameters, etc..

Development plan and timeline

  • Partitioning of tasks
  • Team member responsibilities

Rubric

Software Design

Software Design

Criteria Ratings Pts

This criterion is linked to a Learning OutcomeClarity and WritingCovers the logical construction of the document, as well as the writing itself (grammar, spelling, formatting).

5 to >4.0 pts

Full Marks

The writing is clear and correct — sentences are constructed appropriately, easy to read, and few to no spelling or grammatical errors. The logical flow of the document is intuitive and easy to follow.

4 to >2.0 pts

Clean writing, can improve organization

The content is appropriately written, but the logical flow of the document could be improved to make the content easier to follow.

2 to >0 pts

Content and flow need work

The writing and flow make the document difficult to follow and appear unfinished.

5 pts

This criterion is linked to a Learning OutcomeDesign DiagramUML Class diagram of software design.

5 to >4.0 pts

Full Marks

UML class diagram of complete design present, complete with class names, attributes, operations, and connections between classes.

4 to >1.0 pts

Can improve

Incomplete UML Class diagram present, or architectural diagram present but not UML Class diagram.

1 to >0 pts

Missing

Information not present.

5 pts

This criterion is linked to a Learning OutcomeArchitecture DescriptionExplanation of architectural (UML Class) diagram.

5 to >4.0 pts

Full Marks

Complete and clear explanation of entire UML Class diagram, including overview of class, description of attributes and operations.

4 to >1.0 pts

Can improve

Requires more information, or improved clarity.

1 to >0 pts

Missing

Information not present.

5 pts

This criterion is linked to a Learning OutcomeOther InformationDescription, development plan, and timeline.

5 to >4.0 pts

Full Marks

All information present including an overview of the software system, a list of tasks, an estimated timeline to complete the tasks, and which team member(s) is responsible for each task.

4 to >1.0 pts

Can improve

Missing required information.

1 to >0 pts

Missing

Information not present.

5 pts

Total Points: 20

PreviousNext

About the Author

Follow me


{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}