Project work. Stage: Design

Design section

Nature of the solution Marks: 8
In the report, the candidate attempted to list the objectives of the new system. Weak attempt to present the work of the new system as a description or schematically. 1-2
The main objectives of the new system is sufficient, but not all of them are measurable or suitable for decision-making.
Brief overview of the design features, including a brief description of the schematic representation of the process that consist one / some of the following: prototype of the input / output forms, structure diagram, data flow diagram (minimum context level) or system flowchart.
Data structures have been identified but may contain insufficient data.
At least six SMART objects have been defined and complete. A full design specification is included but there may be some errors or logical inconsistencies, for example validation specified may be inadequate or field lengths incorrect.
A well-designed project for a specific problem describing the key aspects of structured solution is presented.
There is clear evidence that a response to the design has been obtained from the client, and any comments have been acted upon.
A clear set of specific and measurable objectives with a detailed and complete design specification, in a set of measurable and appropriate specific objectives, covering all required functionality of the solution or areas of investigation. 
There are also detailed written descriptions of any processes/modules and a clear including prototype with appropriate components, complete definition of any data structures.

Intended benefits

Intended benefits Marks: 2
One valid benefit of the new system has been identified and explained. 1
The benefits of the new system have been comprehensively described. 2

Limits of the solution

Limits of the solution Marks: 2
One valid limitation of the new system has been identified and explained. 1
The limitations of the new system have been comprehensively described. 2

Project work. Stage: Design

Step 1. SMART objectives

Provide a list of SMART objectives suitable for implementing the new system.

Step 2. Data Flow Diagram

Nature of the solution
(Give a short introduction before designing. What are you going to do? Based on what?)
(Develop a DFD. Do not forget about the basic rules of construction of DFD.)

Step 3. Entity Relationship Diagram

Add annotation before inserting ERD.

Develop an ERD based on the data stores you specified in DFD. The number of tables in the DFD must match the number of tables in the ERD.

Use one-to-one, one-to-many relationships. If you use "many-to-many", it means your database will be not normalise.

Step 4. Data dictionary

Build Data dictionary for each table which you used in ERD.

Step 5. Flowcharts

Design flowcharts according to the DFD processes. The number of flowcharts is equal to the number of processes. Each flowchart must be annotated.

Step 6. Menu structure

Develop a hierarchy of modules as you plan to place them in the project. This can be the site menu, the main menu of the program.


Step 7. Prototyping

Main window

Develop a prototype of the future application. Template only, no content. Perform it efficiently, all lines should be straight, the elements should be clear. You can design it on paper or in editors using shapes. Insert a photo / screenshot into the report. Don't forget to write an annotation before prototyping.


Next, attach proof that the client saw the prototype and approved it in the form of a business letter.

Input and Output forms

Develop a prototype of the input and output forms that you plan to use in the new system.

An example of an input form for adding a new user to the system

Step 8. Hardware and software requirements

Based on the above data, develop minimum hardware and software requirements in the design of a new system.

Fill in the tables:

Hardware requirements

Device Characteristics  Purpose of using

Software requirements

Software Purpose of using

Step 9. Intended benefits

List all expected benefits of the new system in a list.

Describe each item in detail "what is the advantage over the old system?"

Benefits Description

Step 10. Limits of the solution

Specify a list of all the limitations of the new system, ie functions that it cannot perform. Describe in detail what the restrictions are.

Limit Description


Категория: Stages of SDLC | Добавил: bzfar77 (22.11.2020)
Просмотров: 853 | Теги: Intended benefits, Input, Limit of the scope solution, data dictionary, SMART objectives, prototyping, design, ERD, menu structure, Output, SDLC, data flow diagram, Flowchart, dfd | Рейтинг: 0.0/0
Всего комментариев: 0