Scribd
Upload
82 views7 pages

Format - For - SDI - Report Andrubric - Jan2020 PDF

This document provides guidelines for submitting a software design and integration project report. The report should include: 1) A description of the project process including an introduction, problem statement, and storyboard. 2) A description of the system architecture using use case diagrams, class diagrams, and event flows to explain the design. 3) A description of design patterns and a user manual to explain the system functionality. 4) A discussion of benefits, recommendations for future enhancements, and a bibliography. The report is due by a specified date and will be assessed based on the quality of the documentation and a presentation of the project.

Uploaded by

mrevilsakura
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
82 views7 pages

Format - For - SDI - Report Andrubric - Jan2020 PDF

This document provides guidelines for submitting a software design and integration project report. The report should include: 1) A description of the project process including an introduction, problem statement, and storyboard. 2) A description of the system architecture using use case diagrams, class diagrams, and event flows to explain the design. 3) A description of design patterns and a user manual to explain the system functionality. 4) A discussion of benefits, recommendations for future enhancements, and a bibliography. The report is due by a specified date and will be assessed based on the quality of the documentation and a presentation of the project.

Uploaded by

mrevilsakura
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/ 7

Project Guidelines FOR Documentation

ISB37603: Software Design and Integration

Softcopy REPORT that contains:

Title of the project

1. Description of process (introduction, problem statement, story board)

Project Introduction

Briefly explain about your system.


(Max: 3 paragraphs)

i. Problem Statement
ii. Aim and Scope of the project
iii. Technology used (language/database/file/applet etc.)

iv. Storyboard

2. Description of system architecture (system Design- use case, class diagram, event flow)

Explanation about your model design

3. Description of design patterns (user manual of your system)

Project Implementation
Write the user manual for your system – explain the flow of the process from your
system.

Explanations for every functions and modules

Discussion:

Elaborate how the design principles and design pattern involved in your project. (Based on
the flow of system)
Example

a) Abstract Factory Design Pattern


Sample Code:
4. Benefit of the system, recommendations for future enhancement, bibliography /
references

i. Benefit of the project


ii. Conclusion

References
List of books and search engines
2 0r 3 materials

Submission items

Requirements:

 Presentation Date: (During Class Session)


 2/6/2020 L01
 3/6/2020 (Wed –L02)
 Report submission: online via VLE
 Due Date: 7/6/2020 (Sunday)
Assessment - Mini Project SDI JAN 2020
Students Name:

Group :
Project Title:

Factors Marks
Description of process (introduction, problem statement, story board ) 20%

Did you identify and evaluate suitable tools? Did you make good (sensible)
choices? Did you describe the decisions you took in abstracting higher-level
models from the code? Did you critique your process, and reflect on what you
learned?

Description of system architecture(system Design- use case , class diagram,


30%
event flow)
 Did you clearly show the overall architecture? Is your architecture an accurate
representation of the design of the system? Did you critique the architecture, identifying
both strengths and weaknesses? Did you make good use of UML sketches to make your
points?
 Did you provide UML diagrams with enough detail to see the design of the entire system at
least down to class names? Have you eliminated other detail to ensure these diagrams
are still readable? Did you make good use of different UML modeling constructs to
describe the system?
Description of design patterns (user manual of your system) 30%

Did you identify at least three design patterns? Are these patterns genuine? Did
you clearly show how the pattern is implemented in the code? Do your UML
diagrams correspond accurately to the code? Did you show both the static and
dynamic views for these patterns?

Ability to summarize and explain each function properly.:


Interface design (friendliness, color etc.)
System Features and Facilities
Overall functionality (correctness, error free, robust, etc.)

Benefit of the system, recommendations for future enhancement, bibliography


/ references
20%
Conclusion – accomplishment & experience gained
Suggestion – future development & other benefits

Total 100%
Presentation 30%
The style of your presentation, including language, grammar, clarity of the
presentation, layout and legibility of the models, etc. (10% - Language; 20% -
Style and clarity)

Total 30%
Presentation

Make sure you are well prepared for the presentation. Each group member has to participate during
the presentation. Each group will be given 12 minutes to present their work. So remember to
organize your presentation so that you can fully utilize your time. There will be an additional 3
minutes for questions and answers after each presentation

You might also like