S.

JOHN CHRISTOPHER, TEAM LEADER, BURNING GLASS TECHNOLOGIES

SOFTWARE ENGINEERING PROCESSES

Application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software
Requirements

Design

Coding/Construction

Testing

Implementation & Maintenance

Modular Design
Subdivides into smaller parts

Create Independent Smaller Units

Use in different systems

DESIGN HEURISTIC
Set of rules and advise about good and bad design solutions Based on practical experiences. GENERAL - without involvement of the users evaluate by design. APPLICATION SPECIFIC - can only be evaluated with active participation by the users.
General aspects

Application specific aspects

GENERAL
1. Disposition of the screen area 2. Orientation and navigation

APPLICATION
1. Process of user interaction

3. Control and feed-back

2. Simultaneous presentation

4. Input

3. Emphasise what is important

5. Readability

4. Quick commands and shortcuts

6. Errors and help

5. Speak the language of the user

7. Use of colours

ARCHITECTURAL DESIGN
The software architecture of a system is the set of structures needed to reason about the system, which comprise software elements, relations among them, and properties of both. Architecture description languages
AADL Architecture Analysis & Design VIEW POINTS
Functional/logical viewpoint

Code/module viewpoint

Development/structural viewpoint

Language (SAE standard) Wright (developed by Carnegie Mellon)

Acme (developed by Carnegie Mellon)
Darwin (developed by Imperial

Physical/deployment/install viewpoint

User action/feedback viewpoint

Data view/data model

College London)

Other Design Principles..

Data Design, User Interface Design, Real Time Software Design,

System Design

UML
Unified Modeling Language (UML) is a

standardized general-purpose modeling language in the field of object-oriented software engineering.

UML DIAGRAMS

CLASS DIAGRAMS Describes the structure of a system by showing

the system's classes, their attributes, and the relationships among the classes.

OBJECTDIAGRAMS Describes how a software system is split up into

components and shows the dependencies among these components.

ACTIVITY DIAGRAMS
Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency
Rounded rectangles represent activities; Diamonds represent decisions; Bars represent the start (split) or end (join) of concurrent activities; A black circle represents the start (initial state) of the workflow; An encircled black circle represents the end (final state).

USE CASE DIAGRAMS

Graphical representation of a user's interaction with the system

Use Case - defining interactions between a role

(known in UML as an "actor") and a system, to achieve a goal.

Actor - specifies a role played by a user or any other

system that interacts with the subject

USE CASE DIAGRAMS

SEQUENCE DIAGRAMS
How processes operate with one another

In what order the processes operate with one another.

It shows Object interactions arranged in time sequence Sequence diagrams are sometimes called event diagrams, event scenarios, and timing diagrams.

SEQUENCE DIAGRAMS