CS507 Assignment # 3 Solution

Information System (CS507)
Spring 2010
Assignment No. 3
Due Date:
Your assignment must be uploaded/submitted before or on 20th May 2010.
Max Marks: 20
Uploading instructions:
Please view the Assignment Submission Process document provided to you by the Virtual University for uploading assignments.
The assignment should be in .doc format.
Save your assignment with your ID (e.g. bx020200786.doc).
The assignment submission through email is highly discouraged.
Rules for Marking:
It should be clear that your assignment will not get any credit if:
The assignment is submitted after due date.
The submitted assignment file is corrupted.
The assignment is copied.
The assignment material is directly copied from internet.
Note:
Your answer must follow the below given specifications. You will be assigned no marks if you do not follow these instructions.
Font style: "Times New Roman"
Font color: "Black"
Font size: "12"
Bold for heading only.
Font in Italic is not allowed at all.

Q. 1: How can you describe the factors which will ensure the successful implementation of SDLC? Explain at least three.

(Marks: 10)
Answer :( 3.33+3.33+3.33)


Management Support
Developers/system designers need to have the support of the management as much as possible since the management will dictate whether they need the product or not.
Technical and Business Expertise
There are regular programmers and there are really smart programmers who just know what to do even when the software’s objective is presented for the first time. These programmers know what SDLC model to use together with the languages or toolkits that need to be learn to ensure this program is a success. On the other hand, business expertise is also important in software development cycle since they will dictate the demand for particular software. Business expertise is also important in SDLC since they will determine whether the software will eventually be a factor in time and money saving.
Proper Documentation/ Deliverables for Maintenance
Granting the results of the software development is a success; it’s time to place them in all in papers. Success in building software will only be gauged once they are released to the pubic with ease. Although there will be problems, it’s up to the developers to maintain these programs until these are decommissioned. If worst comes to worst and it has to go back to the drawing board, documentation will tell the developers where they might have done it wrong.
Security
Security should be the number priority of any developers. The ability to handle information and protect them from attack will tell how professional the business is. It’s important to look for these defects before they are actually released to the public.
Q. 2: List down the pros and cons of Incremental Model? Also mention when to use the Incremental Model?
(Marks: 10)
Answer :( 3.33+3.33+3.33)

Incremental Model Pros
Working functionality is produced earlier – computation of value to cost ratio
Reduces risks of change in user requirements
Provides clients flexibility in decision making.
Risk management is incremental
Smaller scope for change in user requirements
Develop high-risk or major functions first
Each release delivers an operational product
Customer can respond to each build
Lowers initial delivery cost
Initial product delivery is faster
Customers get important functionality early
Risk of changing requirements is reduced
Incremental Model Cons
Larger picture cannot be seen until the entire system is built
Difficult to break down the total system at early stage of product development to determine reasonable increments
Requires good planning and design
Total cost of the complete system is not lower
When to use the Incremental Model
Need to reduces risks of change in user requirements and reduce program complexity.
Provides clients flexibility in decision making
A need to get basic functionality to the market early
On projects which have lengthy development schedules