Page 38 - SKM4949

4.5 System design
The design is concerned with presenting the design of the artifact developed and justifying how it should meet the identified requirements. It is likely to consist of three parts:
1. how and why the design has been carried out – the approach and notation used, etc;
2. theconceptualleveldesign;
3. communicationanddescriptionofthedesign.
As appropriate, alternatives considered may be discussed with justification for the approach taken. The design should be expressed and detailed in a suitable form.
4.6 Architectural design
The architectural design is concerned with understanding how a system should be organized and designing the overall structure of that system, i.e. it involves identifying major system components and their communications.
4.7 Object Oriented Design (not everyone will implement OOD) it should be subject to the nature of the project.
4.7.1 Structural Static Models
The diagrammatic representation depends on the modeling language that
you use. For example, class diagram, DFD, ERD, etc.
For research-based or simulation project you probably need the (detail) flowchart, experimental design, etc.
4.7.2 Dynamic Models
The student may present Activity diagrams, Statechart diagrams or
Sequence diagrams. For example, a sequence diagram may be used to add detail to use-cases by showing the sequence of event processing in the system (shows the sequence of interactions that take place during a particular use case or use case instance). The sequence diagrams are used to model the interactions between the actors and the objects within a system.
4.8 Data Modeling
The databases design or the developed algorithms should be presented here. This section will reveal the final design and detailed description of all the DBMS files and non-DBMS files. This section should contain criteria for the data elements, including specific values, range of values, mandatory/optional, alphanumeric values, and length.
34