ISWE Tips/Note

Software- program that control the operation of the computer.

Software engineering- is an engineering discipline that is concerned with all aspects of

software production with A principle of designing and developing software based on SDLC.)
ISWE Finals Tips (given by lecturer)

Requirement engineering- process of establishing the services that the customer requires
from a system and the constraint under which it operate and developed

Type of requirement

User requirement- statement in natural language plus diagram of the services the system
provides and its operational constraints (customer)

*client manager/system end-user/client engineer/contractor manager/system architects

System requirement- structured document setting out detailed description of systems

function, services and operational constraints (client and contractor)

*system end-user/client engineer/system architect/software developer

Functional requirement and non-functional requirement and Domain requirement

(FR) Statement of services the system should provide how system react to part input/behave
in part situation/state what system cant do [user/system requirement]

(NFR) constraint on the services/function by the system (time constraints, development

process constraint and standard) [apply to system than individual features/services]

*(NFR) Product requirement (execution speed, reliability), organizational requirement

[policies/procedure] (process standard used, implementation requirement), external
requirement (interoperability requirement, legislative requirement)

Good Requirement- Modifiable (can change without need of modify others), Current (up-to-
date), Complete (fully describe the functionality), Attainable ( specific f need to achieve),
verifiable (req. has been met)

Case Tool (Computer Aided Software Engineering)

Upper Case Tool- system planning, system analysis and general system design

(support modelling process and produce logical design of the information system)

Lower Case Tool- detailed system design, system implementation and system support

(speed the development process by generating source code based on logical model)

Draw Gantt Chart

Project Management s/w (s/w dev. Sub to budget/schedule constraint)- concerned with
activities involved in ensuring that s/w is delivered on time/schedule and met the requirement
of organization developing/ procuring the s/w

*project consist of interrelated activities which are to be executed in a certain order before the
task is completed

Phases of Project Management

Pert Chart (Program Evaluation Review Technique) navy- [Critical Path Method] private
industry similar needs

*Activity on Arrow/Node

Use case modelling- developed originally to support requirement elicitation and now
incorporated into UML Sequence diagram

Software Testing- process of exercising program with specific intent of finding error prior to
delivery to the end user.

Testing- error/requirement conformance/performance/an indication of quality

Strategic Approach

Effective technical review- to eliminate error before testing commence

Testing/debugging- debugging most accommodated in testing strategy

V&V-verification (set of task s/w implement correctly in specific function) & validation (set
of different task that ensure s/w has been built that requirement has met the customer)

*developer/independent tester

Testing strategy- Unit, Integration, Validation, System