We are here with you hands in hands to facilitate your learning & don't appreciate the idea of copying or replicating solutions. Read More>>

Looking For Something at vustudents.ning.com? Click Here to Search


+ Link For Assignments, GDBs & Online Quizzes Solution


+ Link For Past Papers, Solved MCQs, Short Notes & More

Dear Students! Share your Assignments / GDBs / Quizzes files as you receive in your LMS, So it can be discussed/solved timely. Add Discussion

How to Add New Discussion in Study Group ? Step By Step Guide Click Here.

CS615 Software Project Management Assignment No 1 Solution & Discussion Due Date:06-05-2014

Assignment No. 01
Semester: Spring 2013

CS615 Software Project Management


Total Marks: 15


Due Date: 06/05/2014


Objectives of Assignment:


  • Your Assignment no 1 covers Lec#1 to Lec#8 Complete.
  • You would learn the project and its management along with software process models.


Uploading instructions:


Please view the Assignment Submission Process document provided to you by the Virtual University for uploading assignments.


  • Your assignment must be in .doc format.(Any other formats like scan images, PDF, Zip, rar, bmp, docx etc will not be accepted).
  • No assignment will be accepted through email.


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 does not open or file is corrupted.
  • Your assignment is copied from internet, handouts or from any other student

      (Strict disciplinary action will be taken in this case).





Question 1

Identify from the given situations, which one is project and which one is a process? Any Five (1+1+1+1+1=5,  1 Mark Each)


  1. Designing a map for software house.
  2. Changing the tyre of a vehicle.
  3. Developing Core computer based system.
  4. Salary calculation of employees.
  5. Deploying a traffic plan system.
  6. Mentoring a SPM Class.
  7. Developing an Assignment.
  8. Software Development for Pharmaceutics.







Question no 2:                                                                                                                                10 Marks

Suppose you are required to develop an online Garments Inventory Management System for providing different online services to the customers and the staff, which is considered as the complex system as along with sales, purchase record is concerned. The customers demand keeps on changing with the demanding requirement of the market trend. You being a Software Project Manager facing different requirements changing time to time by the management of the inventory at store. You are leading a team of software engineers and you need to choose the process model first for having an effective design model before proceeding to coding phase. Which process model you choose and why you choose the selected process model? State with any three solid reasons.

 4 +  (2*3= 6) = 10 Marks


NOTE: Submit “.doc” file only. Every student should provide his/her own work, exact copying of the assignment (or some portion of the assignment) from the internet or other students will lead to copy case and zero marks will be awarded. Different softwares will be used to check plagiarism in assignments. Do not put any query on MDB about this assignment, if you have any query then  email at CS615@vu.edu.pk



Your assignment must be uploaded/submitted on or before 6 th May  2014.


+ How to Follow the New Added Discussions at Your Mail Address?

+ How to Join Subject Study Groups & Get Helping Material?

+ How to become Top Reputation, Angels, Intellectual, Featured Members & Moderators?

+ VU Students Reserves The Right to Delete Your Profile, If?

See Your Saved Posts Timeline

Views: 1717


+ http://bit.ly/vucodes (Link for Assignments, GDBs & Online Quizzes Solution)

+ http://bit.ly/papersvu (Link for Past Papers, Solved MCQs, Short Notes & More)

+ Click Here to Search (Looking For something at vustudents.ning.com?)

+ Click Here To Join (Our facebook study Group)


Replies to This Discussion

Please Discuss here about this assignment.Thanks

Our main purpose here discussion not just Solution

We are here with you hands in hands to facilitate your learning and do not appreciate the idea of copying or replicating solutions.

For the 1st question here is the answer please discuss whether it is right or wrong . have i used the correct logic in defining all 8 points .

1. Designing a map for software house. 
2. Changing the tyre of a vehicle. 
3. Developing Core computer based system.
4. Salary calculation of employees.
5. Deploying a traffic plan system. 
6. Mentoring a SPM Class.
7. Developing an Assignment.
8. Software Development for Pharmaceutics.

Dear Tariq bhai achi kawish hay aap ki...... Admired it..... Please also help in 2nd question also.... please, please, please......

what about 2nd question 

there are 2 model which we use 

(1) water fall

(2) spiral

ab in ma sa he 1 ko define karna ha both are mostly same 

2nd question m kon sa model aye ga?plz tell me 

g ya thek kia hwa h 

is ka kon batay ga lagta ha kasi ka subject nahi ha ya 

Prototype model is correct

deployment process nhi hta??

idea of 2nd Questions.

The thing being asked us in this question is to analye the Process Models by our requirements of creating a new system of Garments by managing sales and purchase record, documentation and changing demand of all Customers in the current 21st century .

Here are few definitions and advantages and disadvantages of Models ...... evaluate urself on the given situation and than pick up the correct answer for that and give 3 Solid reasons for choosing that 1 Process Model.


The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-sequential life cycle model.  It is very simple to understand and use.  In a waterfall model, each phase must be completed fully before the next phase can begin.   At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. In waterfall model phases do not overlap.

Advantages of waterfall model:

  • Simple and easy to understand and use.
  • Easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.
  • Phases are processed and completed one at a time.
  • Works well for smaller projects where requirements are very well understood.

 Disadvantages of waterfall model:

  • Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.
  • No working software is produced until late during the life cycle.
  • High amounts of risk and uncertainty.
  • Not a good model for complex and object-oriented projects.
  • Poor model for long and ongoing projects.
  • Not suitable for the projects where requirements are at a moderate to high risk of changing.

When to use the waterfall model:

  • Requirements are very well known, clear and fixed.
  • Product definition is stable.
  • Technology is understood.
  • There are no ambiguous requirements
  • Ample resources with required expertise are available freely
  • The project is short.


The basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements. By using this prototype, the client can get an “actual feel” of the system, since the interactions with prototype can enable the client to better understand the requirements of the desired system.  Prototyping is an attractive idea for complicated and large systems for which there is no manual process or existing system to help determining the requirements. The prototype are usually not complete systems and many of the details are not built in the prototype. The goal is to provide a system with overall functionality.

Advantages of Prototype model:

  • Users are actively involved in the development
  • Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed.
  • Errors can be detected much earlier.
  • Quicker user feedback is available leading to better solutions.
  • Missing functionality can be identified easily
  • Confusing or difficult functions can be identified
    Requirements validation, Quick implementation of, incomplete, but
    functional, application.

Disadvantages of Prototype model:

  • Leads to implementing and then repairing way of building systems.
  • Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans.
  • Incomplete application may cause application not to be used as the
    full system was designed
    Incomplete or inadequate problem analysis.

When to use Prototype model:  

  • Prototype model should be used when the desired system needs to have a lot of interaction with the end users.
  • Typically, online systems, web interfaces have a very high amount of interaction with end users, are best suited for Prototype model. It might take a while for a system to be built that allows ease of use and needs minimal training for the end user.
  • Prototyping ensures that the end users constantly work with the system and provide a feedback which is incorporated in the prototype to result in a useable system. They are excellent for designing good human computer interface systems.


In incremental model the whole requirement is divided into various builds. Multiple development cycles take place here, making the life cycle a MULTI WATER FALL CYCLE.  Cycles are divided up into smaller, more easily managed modules.  Each module passes through the requirements, design, implementation and TESTING phases. A working version of software is produced during the first module, so you have working software early on during the SOFTWARE LIFE CYCLE Each subsequent release of the module adds function to the previous release. The process continues till the complete system is achieved.

Advantages of Incremental model:

  • Generates working software quickly and early during the software life cycle.
  • More flexible – less costly to change scope and requirements.
  • Easier to test and debug during a smaller iteration.
  • Customer can respond to each built.
  • Lowers initial delivery cost.
  • Easier to manage risk because risky pieces are identified and handled during it’d iteration.

Disadvantages of Incremental model:

  • Needs good planning and design.
  • Needs a clear and complete definition of the whole system before it can be broken down and built incrementally.
  • Total cost is higher than waterfall.

When to use the Incremental model:

  • Requirements of the complete system are clearly defined and understood.
  • Major requirements must be defined; however, some details can evolve with time.
  • There is a need to get a product to the market early.
  • A new technology is being used
  • Resources with needed skill set are not available
  • There are some high risk features and goals.


The spiral model is similar to the INCREMENTAL MODEL with more emphasis placed on risk analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A software project repeatedly passes through these phases in iterations (called Spirals in this model). The baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each subsequent spirals builds on the baseline spiral.Requirements are gathered during the planning phase.  In the risk analysis phase, a process is undertaken to identify risk and alternate solutions.  A prototype is produced at the end of the risk analysis phase.

Software is produced in the engineering phase, along with TESTING at the end of the phase.  The evaluation phase allows the customer to evaluate the output of the project to date

Advantages of Spiral model:

  • High amount of risk analysis hence, avoidance of Risk is enhanced.
  • Good for large and mission-critical projects.
  • Strong approval and documentation control.
  • Additional Functionality can be added at a later date.
  • Software is produced early in the software life cycle.

Disadvantages of Spiral model:

  • Can be a costly model to use.
  • Risk analysis requires highly specific expertise.
  • Project’s success is highly dependent on the risk analysis phase.
  • Doesn’t work well for smaller projects.

 When to use Spiral model:

  • When costs and risk evaluation is important
  • For medium to high-risk projects
  • Long-term project commitment unwise because of potential changes to economic priorities
  • Users are unsure of their needs
  • Requirements are complex
  • New product line
  • Significant changes are expected (research and exploration)

NOTE: (HINT)    

u can guess the correct option from the portion of above paragraph that WEHN TO USE CERTAIN MODEL IS BEST.

Mera MATLAB ha ka ap uper dia gay paragraph SECTION (WHEN TO USE CERTAIN MODEL) main se evaluate ker sakte hain ka kab kis waqt, kis situation main kon sa MODEL USE KERNA HA.

Prototype model



Today Top Members 

© 2020   Created by +M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service