Scribd
Upload
31 views4 pages

12 - Software Development

Uploaded by

Aayan Ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views4 pages

12 - Software Development

Uploaded by

Aayan Ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Development

Steps of the program development cycle:


1. Analysis
 Includes the research done to identify what is required from the program/ Figuring out the
intended purpose of the program.
2. Design
 Refers to how each task is to be performed and how the tasks work when implemented.
 This is done using structure charts, pseudocode and flowcharts etc.
3. Coding
 The writing of the program in a programming language.
4. Testing
 The code is run many times with sets of test data to make sure that it fulfills the tasks it
was made for.
5. Maintenance
 It is done to ensure that the program works flawlessly such as correcting errors that may
come up after or keeping it up to date.
 These can be corrected via updates or manually editing the source code.
Models of the Program Development Cycle:
1. Waterfall Model
 Each stage is completed before the next one is started.
 It is suitable for small scale projects whose requirements are well known.
 It is easy to manage and use.
 However, it is difficult to change the requirements later on.
 It is not suitable for large projects.
2. Iterative Model
 The program development cycle runs until the whole system has been developed.
 It is suitable for projects whose requirements are majorly known.
 It is easy to develop, test and debug.
 However, the whole program needs to be broken down.
 It is not suitable for small projects.

3. Rapid Application Development Model


 It develops different parts of the requirements in parallel using prototyping.
 It is suitable for complex projects whose requirements are minimally known.
 It reduces the program development time and is easy to edit.
 However, modular programming must be done and it requires high programming skills.
 It is not suitable for small projects.

State Transition Diagram (STD):

 It shows all the states, inputs and outputs in an object.

1
Software Development
 The state is shown in a circle. The transition is shown with an arrow.
 For example, a table lamp has 2 states, ON and OFF. These states are triggered by
repeated inputs of switch pressed.
Structure Charts:

 They are modelling tools which are used to decompose a problem into sub problems.
 They show the linkage between different modules and the passing of parameters between the
modules.
 The modules are linked to each other by arrows.
 They represent the hierarchy of modules.
 They represent selection, repetition, iteration.
Program Fault:
An error which makes the program do something which it is not supposed to do under certain
circumstances.
Ways of reducing the faults when writing programs:
1. Tested library routines.
2. Modular programming. (Breaking down a problem)
3. Usage of IDE features.
4. Good programming practices like named variables.
Syntax Error:
A statement in the source code which breaks the rules of the language.
Logic Error:
An error in the algorithm which causes the program to behave in an unexpected way.
Run-Time Error:
An error when a program performs an invalid operation such as entering an infinite loop.
White Box Testing:
Testing every path through the code.
Black Box Testing:
Testing the module’s INPUT and OUTPUT.
Trace table is used to record changes.
Integration Testing:
Testing individual modules whether they work together.

Stub Testing:
Makes use of dummy modules for testing.

2
Software Development
Alpha Testing:
Program is tested in house by the development team.
Beta Testing:
Program is tested by a small group of users.
Acceptance Testing:
Used for the complete program to prove to the customer that the program works well for its intended use.
Program Maintenance:
Corrective Maintenance: Correct errors during development.
Perfective Maintenance: Improve the performance of a program.
Adaptive Maintenance: Update the program to match the current requirements of the user.

3
Software Development

Why a high-level programming language must be translated before it can be run.


The code has to be in machine code before it can be executed.
Methods of finding an error in a program which doesn’t give the desired output.
1. Use white box testing to trace the routes through the program.
2. Use breakpoints to set points to find errors.
3. Use variable watch to look for the contents of the variables.
4. Use of stepping to execute the code line by line.
5. Including OUTPUT statements to output the contents of the variables when the code is running.

You might also like