INF2011S Notes
1.1. MOVING TO DESIGN............................................................2
1.2. SYSTEMS ARCHITECTURE...................................................11
1.3 CLASS DESIGN...................................................................21
1.4 (1) SYSTEMS SEQUENCE DIAGRAMS (SSD)...........................28
1.4 (2) DETAILED SEQUENCE DIAGRAMS (DSD)..........................34
1.5 (A) USER INTERFACE DESIGN..............................................42
1.5 (B) REPORT DESIGN............................................................48
1.6 (A) TESTING AND TEST CASES.............................................52
1.6 (B) SECURITY AND CONTROL...............................................66
,1.1. Moving to Design
Systems Design
The objective is to define, organize, and structure the components of the final
solution to serve as a blueprint for development.
Provides the starting point for systems development.
Provides the starting point for systems design.
Systems Development
Build, test and integrate system components (programming and component
integration) in accordance with chosen computer architecture and methodology.
Systems Implementation
Installing, testing and securing, and backing-up the system.
Process:
Analysis Design Implementation
Waterfall vs agile approach
, 1. Waterfall life cycle: clear transition between two activities (analysis and
design).
2. Agile/iterative approach: analysis of a specific part of the system will come
before its design, but analysis and design may be occurring in parallel.
NOTE: Best approach to use would be the Agile approach.
, Design VS Analysis
Throughout design, team considers new system in respect to
current environment and systems that exists with the organisation as a whole:
Environmental factors (e.g. integrating with an existing system).
Convert data from legacy systems.
Leveraging skills that exist in-house.
Getting UX (user experience) and UI (user interfaces) correct.
Key activities undertaken during design stage:
Examine several design strategies and decide which will be used to build
system.
Detailed design of individual classes and methods.
Designing UI, system inputs and outputs.
Making physical arch decisions regarding hard and software that will be
purchased to support new system.
Levels of Design
1. System Design: deals with the high-level architecture of the system -
structural aspects and standards that affect the overall system.
Hardware, network, and system software infrastructure.
Communication between sub-systems.
Standards for screens, reports, help etc.
2. Detailed design: adds detail to the analysis to provide a detailed system
specification.
Adds detail to analysis to provide detailed system specification.
Class design
Sequence design
UI and report design
Database design
Security and controls design
Design Activities
Describe the environment.
Design the application components.
Design the user interface.
Design the database.
Design the software classes and methods.
1.1. MOVING TO DESIGN............................................................2
1.2. SYSTEMS ARCHITECTURE...................................................11
1.3 CLASS DESIGN...................................................................21
1.4 (1) SYSTEMS SEQUENCE DIAGRAMS (SSD)...........................28
1.4 (2) DETAILED SEQUENCE DIAGRAMS (DSD)..........................34
1.5 (A) USER INTERFACE DESIGN..............................................42
1.5 (B) REPORT DESIGN............................................................48
1.6 (A) TESTING AND TEST CASES.............................................52
1.6 (B) SECURITY AND CONTROL...............................................66
,1.1. Moving to Design
Systems Design
The objective is to define, organize, and structure the components of the final
solution to serve as a blueprint for development.
Provides the starting point for systems development.
Provides the starting point for systems design.
Systems Development
Build, test and integrate system components (programming and component
integration) in accordance with chosen computer architecture and methodology.
Systems Implementation
Installing, testing and securing, and backing-up the system.
Process:
Analysis Design Implementation
Waterfall vs agile approach
, 1. Waterfall life cycle: clear transition between two activities (analysis and
design).
2. Agile/iterative approach: analysis of a specific part of the system will come
before its design, but analysis and design may be occurring in parallel.
NOTE: Best approach to use would be the Agile approach.
, Design VS Analysis
Throughout design, team considers new system in respect to
current environment and systems that exists with the organisation as a whole:
Environmental factors (e.g. integrating with an existing system).
Convert data from legacy systems.
Leveraging skills that exist in-house.
Getting UX (user experience) and UI (user interfaces) correct.
Key activities undertaken during design stage:
Examine several design strategies and decide which will be used to build
system.
Detailed design of individual classes and methods.
Designing UI, system inputs and outputs.
Making physical arch decisions regarding hard and software that will be
purchased to support new system.
Levels of Design
1. System Design: deals with the high-level architecture of the system -
structural aspects and standards that affect the overall system.
Hardware, network, and system software infrastructure.
Communication between sub-systems.
Standards for screens, reports, help etc.
2. Detailed design: adds detail to the analysis to provide a detailed system
specification.
Adds detail to analysis to provide detailed system specification.
Class design
Sequence design
UI and report design
Database design
Security and controls design
Design Activities
Describe the environment.
Design the application components.
Design the user interface.
Design the database.
Design the software classes and methods.
