ISYS3416 – Software Engineering Fundamentals

Assessment 3 – Software Design Document

Aims and Objectives

You will write a design document of the functionality described for your system. Below is the
design proposal template document for an example of formatting and expected headings and
sections.

How to submit:
• Assignment must be in Turnitin with the naming convention
ISYS3416_A3_GroupName

• Original UML diagram must be added as additional file in Canvas (DO NOT
zip all additional files).
 Table of Contents

• Non-functional Requirement
• UI/UX based on Use Case: rẻ rách
• Software Design
• Class Diagrams
• Object Diagrams
• Sequence Diagrams or Data Flow Diagrams
• Management
• Test Plan
• Schedule
• Summary
<This is the template document. Replace any text in <> with your text. There should be no text
surrounded by <> in this document when you are done. Remember, the purpose of this document is
to be useful: not just work to get a grade. A company should be able to use this document to
develop software.
DO NOT include the A2 requirements document. This document is assumed to be part of the A2
Design and Proposal document as appendix A. When referring to the requirements document (A2)
please say “Refer to Appendix A”>

• Non-Functional Requirements
<This section captures non-functional requirements in the customer language.>
• User Interface (individual)
<Each team member should provide information about your user interface(s) based on
the Use Case(s) he/she described in Software Requirement Specification document
before. Provide a design of the user interface including the “look and feel.” You can
make the mockup interface using any software you like. Generate screen shots and
place them here with titles and descriptions. Be sure to refer to your screen shots when
explaining your interface. Provide descriptions and explanations/report on why you
selected this particular interface. Each user interface will be named
Suggested tools below, but you can use any tool you are familiar with:
balsamiq.com (tutorial: www.youtube.com/watch?v=KnZrypOaVCg)
figma.com/ (tutorial: www.youtube.com/watch?v=dXQ7IHkTiMM)

Example:

>
• Performance
<Provide information on how the system will perform you can base it terms of the following:
availability, response time, security, mobility, and maintainability, >
• Constraints
<Provide a general description of any other items that will limit the developer’s options.
These can include:
a) Regulatory policies (e.g. some policies that users need to follow when using the app)
b) Hardware limitations (e.g., signal timing requirements)
c) Interfaces to other applications (e.g. API or XML data sharing)
d) Parallel operation (e.g. what are the operations that need to be supported for parallel
operations without breaking the integrity of the data stored.)
e) Audit functions (e.g. administrators’ ability to choose and filter the user’s desired
dataset)
f) Control functions (e.g. administrators’ ability enable/ disable some functions/features of
the app).
g) Higher-order language requirements (e.g. Java shall be the implementation language
with
Android, Facebook, Google SDK’s.)
h) Signal handshake protocols (e.g., XON-XOFF, ACK-NACK)
i) Reliability requirements (e.g. shall operate on Android v4.0 or higher operating system)
j) Criticality of the application (e.g. How critical the users’ data is)
k) Safety and security considerations (e.g. Information of the users shall be encrypted
before
transferred to database in order to maintain the security of the crucial information about
users.)
 • Software Design
<In this section you will explain your design. You should provide a general overview here of
your design. In each section below, you detail the design. You must also include the .uml or .jpg
files of all your diagrams (Class, Object and Sequence /DFD) in your submission.>

• Class Diagrams
<In an UML tool of your choice (StarUML for example), create class diagrams using your
use cases. Take advantage of the class modeling language to provide a clean design. You
need to consider associations, classes, multiplicity, constraints, attributes, operations, roles,
generalization, aggregation, composition, interface, abstract classes, and association
classes. For your class diagram, you must explain why you (as a team) choose the design
you are submitting. >
• Object Diagrams
< In an UML tool of your choice (StarUML for example), create object diagrams. Be sure
to include object diagrams you created during your design to figure out and verify
multiplicity between classes. You must also provide object diagrams showing any static
structure in your system. An explanation for each object diagram is required. >
• Sequence Diagrams or Data Flow Diagram (individual work)
<In this section, each team member will provide sequence diagrams or data flow diagrams.
Provided titles for your diagrams and a brief description of each diagram. Provide a
decomposition of the subsystems in the software design. >
• Management
• Test Plan
<In this section you will provide a general outline of test plans for the product. Don’t forget to
include this outline and time within your project estimation.>

• Schedule
<Here you will provide timelines and estimates on time to completion of the project. You may
base your estimated time according to the methodology you are planning to use.

<GOOD LUCK!!!>