Software Engineering Paper - Prototyping Model

3670 words 15 pages

Software Engineering (C2002)
TERM 1 2009

? Answer ALL questions.
? Marks will be awarded for good presentation and thoroughness in your approach.
? NO marks will be awarded for the entire assignment if any part of it is found to be copied directly from printed materials or from another student.
? Complete this cover sheet and attach it to your assignment.

Student declaration:
I declare that:

I understand what is meant by plagiarism
The implication of plagiarism have been explained to me by my institution
This assignment is all my own work and I have acknowledged any use of the published or unpublished works of other people.

Student's signature: ??????????????.
…show more content…

Customer produces a set OR group of expectations for the end-product (software system). Alot times when the customer produces such information, it is insufficient for the system developer such that specific information such as input/output or the "operations" for the system software are lacked.

With that, the "Prototyping model" comes in as being the best utilized approach in situations such as this.

In addition, this model allows the software developer to utilize its ability of being able to identify software requirements which are necessary for the engineering of the system software. In a case whereby the first engineered software is made (first of its kind), it is known as a prototype. The prototype model will be used as the default test system until a finalised one is engineered as fully operational system. A lot of times the prototype would come out in 1 or 2 versions with minor use of resources, it may or may not work out but it assists or trains a programmer at the same time.

With a prototype, the software developer would be able to point out the functions that it lacks OR the errors or bugs that occur within the software system itself. Now when these set of information is collected, solutions are generated in each respective area so that he/she is able to utilize the existing applications that were used in its "building" stages to improve or correct these AREAS.

Some of these software could be stand-alone programs or application tools such as


  • System Development Life Cycle
    1362 words | 6 pages
  • Login/Logout System
    3548 words | 15 pages
  • Project management approaches for dynamic environments
    7283 words | 30 pages
  • Information Technology Project Management Appendix Answers
    19468 words | 78 pages
  • Case Study for Management Accounting
    36924 words | 148 pages
  • Marketing Management 14th Edition Test Bank Kotler Test Bank
    173938 words | 696 pages