“Explain COCOMOL model.” You have to solve the question of SMU MBA MI0024 for Software Engineering. MBA students of Information System (IS) of Sikkim Manipal University MI0024 can write the assignment. I already have shared some other MI0024 MBA assignments also such as - Linear Sequential Model and 4GL Technologies.
In this classic book on “software engineering economics,” Barry Boehm [BOE81] introduced a hierarchy of software estimation models bearing the name COCOMO, for constructive cost model. The original COCOMO model became one of the most widely used and discussed software cost estimation models in the industry. It has evolved into a more comprehensive estimation model, called COCOMO II [BOE96, BOE00]. Like its predecessor, COCOMO II is actually a hierarchy of estimation models that address that following areas:
Application composition model: Used during the early stages of software engineering, when prototyping of user interfaces, consideration of software and system interaction, assessment of performance, and evaluation of technology maturity are paramount.
Early design stage model: Used once requirements have been stabilized and basic software architecture has been established.
Post-architecture-stage model: Used during the construction of the software.
The Software Project Plan is a relatively brief document that is addressed to a diverse audience. It must (1) communicate scope and resources to software management, technical staff, and the customer; (2) define risks and suggest risk aversion techniques; (3) define cost and schedule for management review; (4) provide an overall approach to software development for all people associated with the project; and (5) outline how quality will be ensured and change will be managed.
This is, the project team revisits the plan repeatedly – updating risks, estimates, schedules and related information – as the project proceeds and more is learned.
Similarly, the degree of detail contained within the schedule section may vary with the audience and formality of the plan. It is the important to note that the Software Project Plan is not a static document.
In this classic book on “software engineering economics,” Barry Boehm [BOE81] introduced a hierarchy of software estimation models bearing the name COCOMO, for constructive cost model. The original COCOMO model became one of the most widely used and discussed software cost estimation models in the industry. It has evolved into a more comprehensive estimation model, called COCOMO II [BOE96, BOE00]. Like its predecessor, COCOMO II is actually a hierarchy of estimation models that address that following areas:
Application composition model: Used during the early stages of software engineering, when prototyping of user interfaces, consideration of software and system interaction, assessment of performance, and evaluation of technology maturity are paramount.
Early design stage model: Used once requirements have been stabilized and basic software architecture has been established.
Post-architecture-stage model: Used during the construction of the software.
The Software Project Plan is a relatively brief document that is addressed to a diverse audience. It must (1) communicate scope and resources to software management, technical staff, and the customer; (2) define risks and suggest risk aversion techniques; (3) define cost and schedule for management review; (4) provide an overall approach to software development for all people associated with the project; and (5) outline how quality will be ensured and change will be managed.
This is, the project team revisits the plan repeatedly – updating risks, estimates, schedules and related information – as the project proceeds and more is learned.
Similarly, the degree of detail contained within the schedule section may vary with the audience and formality of the plan. It is the important to note that the Software Project Plan is not a static document.
0 comments:
Post a Comment