You have a privilege to create a quiz (QnA) related to this subject and obtain creativity score...
Software Design Description (SDD) or sometimes named as Software Design Specification usually follows Business Requirements and provides more details on how business goals are going to be implemented.
It is a good idea to keep business goals in focus while describing implementation details.
Software Design Description can include some system architecture artifacts unless specific set of architecture documents is provided.
Software Design Descriptions consist of text and graphical information. A picture is better than thousand words! The pictures also have their own language: Universal Modeling Language (UML).
See below several examples of UML notations.
Design document target several audiences and should provide multiple points of view:
- Detail functionality with a recommended Use Cases Diagram
- Data architecture with a recommended Data Table Diagram
- System Architecture Views including component, services, and other architecture diagrams (see an example in the previous section)
- The next level diagrams usually describes component or business service details with the most common:
---- Class Diagram ? represents classes with their relationships: inheritance and association
See two examples below describing the order related classes and a hierarchy: person, customer, employee, which also has subclasses, such as OE Clerk and CS Rep.
There is a legend at the bottom of the illustration. The legend describes the notations used in the diagram, including associations with multiplicity numbers.
For example, Person and Address associated as 1 ? 1, which means that every person has one address. A Customer can have 2 and more Addresses (2*) and 1 and more Orders (1*).
Was it clear so far?
----- Sequence Diagram ? describes a sequence of activities ? methods performed by several classes in one of Use Cases.
The illustration below describes the events from the Order to the Payment and in-between.
Horizontal lines are the messages of services or class methods performed in that sequence by the classes or services that are located at the top.
Vertical lines correspond time flow.
---- Collaboration Diagram describes component interactions and has some similarity with the Sequence Diagram.
Assignments: - Read more on Software descriptions - Download and read an example of Software Design Description - Follow an example of modified Business Requirements with more SEARCH criteria and create a MS Word copy and add specific SEARCH criteria to all sections.
--- At this point think as a business analyst. What features a user would like to add to existing descriptions?
Include in the requirements the lines/paragraphs such as,
-Allow users to SEARCH for content titles
-Allow users to SEARCH for keywords in the content
-Allow privileged users to SEARCH for user names, email addresses, etc.
--- The purpose is to learn how to look at an application from business point of view.
--- Please color new things proposed in the document by green color.
In each section provide details that you feel are necessary. Then Upload your MS Word document.
- Create 2 QnA related to the material and email to dean@ituniversity.us
