Principles of Software Engg.

2658 words 11 pages
University of Ballarat
GRADUATE SCHOOL OF INFORMATION TECHNOLOGY
AND MATHEMATICAL SCIENCES

ITECH6501 Principles of Software Engineering

Name: Abdulhadi Zawi (30088958)

Individual Assignment - 20 marks – refer to Course Description for weighting

Semester 2011/05 Report Due Date: Refer to course description

In this first assignment, TWO software development methodologies will be examined using the first four laws given in the prescribed text.

Glass’ law Requirement deficiencies are the prime source of project failures. (LI)

Boehm’s first law Errors are most frequent during the requirements and design activities and
…show more content…
Boehm’s second law: In Agile software development, each iteration acts as a prototype of the actual system, and hence user can easily identify the potential problems in the early stage of development. The initial prototype of the system helps the development teams identify the initial set of requirements to start working with. They develop the prototype to capture the requirements and then in each iteration a small number of new requirements are developed and delivered to the customer to get their feedback. If there is a problem in the interface the customer sees it as soon as a new iteration is completed and can easily get it corrected.

Davis’ law: In Agile software development methodology the importance is put on the working software delivered to the customer and all the activities revolve around this. The models are made just to understand and communicate some concepts about the software to be developed. These models can be detailed enough to expand the whole wall of an office or it can be a simple diagram to tell other developers how one has tackled some specific problem. The purpose remains the same; i.e. to help understand and build the system. Any level of model can not be a substitute for everything. There is no “One size fits all”.

2. Your first task is to describe each software development methodology clearly and completely in your own words. You may use diagrams, examples or UML to help you do this. [2 + 2 = 4

Related

  • Valve Software
    1894 words | 8 pages
  • Smith Consulting Software
    4486 words | 18 pages
  • Crm Software
    1415 words | 6 pages
  • Market Analysis for Product Software
    1263 words | 6 pages
  • La Jolla Software
    1249 words | 5 pages
  • The Bluesky Software Consulting Firm
    2118 words | 9 pages
  • Computer Hardware and Software
    1472 words | 6 pages
  • Software Piracy
    2175 words | 9 pages
  • Software Defined Networks
    4064 words | 17 pages
  • Upgrading Software with Vbscript
    1513 words | 7 pages