Preview

Assignment 01

Best Essays
Open Document
Open Document
2597 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Assignment 01
Abstract
In this IT Era, most of people adopt to internet and most of the information systems to make their lives comfortable. According to the high demand and competition of the IT field, software, hardware and IS are released day by day. When developing a software/ hardware/ IS what are the procedures need to follow?, how it is possible to make that more reliable? There are some methodologies need to follow up to get best outcome with development projects, this paper presents those methodologies and some laws related to them.
Keywords: Waterfall Methodology, Prototyping Methodology, Glass’ law, Boehm’s first law, Boehm’s second law, Davi’s law, Moore’s law
1. INTRODUCTION
This document presents about methodologies for development projects and few lows which are related to them. More over this presents some explanations of Waterfall methodology and Prototyping methodology as well Glass’s law, Boehm’s first and second law, Davi’s law and Moore’s law with examples. Furthermore this will discuss on appropriateness of using those laws and those methodologies with real time examples.

2. DESCRIPTION OF FOUR LAWS
2.1. Glass’ Law: “Requirement deficiencies are the prime source of project failures.”
Glass’ Law is talking about the lack of requirement gathering/ analysing of a project. Requirements determine the properties of a project and all processes are based on the requirement. Moreover requirements are the objectives that must be met in any project. Incomplete, improper or erroneous requirement causes most project failure and the reason after that are different needs of various user groups of people. Practically requirements are not perfect and these problems are repeating by generation to generation and will not disappear with the technological development.
For an example, baggage handling system for the Denver airport caused requirement deficiencies. This project failed because they took decisions underestimating complexity of the project



References: [1]. Brown, J. (1997). HCI and Requirements Engineering - Exploring Human-Computer Interaction and Software Engineering Methodologies for the Creation of Interactive Software. SIGCHI, 29(1). Retrieved from http://homepages.cwi.nl/~steven/sigchi/bulletin/1997.1/brown.html#HDR2 [2]. Calleam Consulting Ltd. (2008).Denver Airport Baggage Handling System Case Study. Retrieved on 31st March 2013 from http://www5.in.tum.de/~huckle/DIABaggage.pdf [3]. Enders, A. & Rombach, D. (2003). A Handbook of Software and Systems Engineering. Harlow, England: Pearson Education Limited. Available from ATMC Moodle. [4]. Howcroft, D. & Carroll, J. (n.d.). A Proposed Methodology for Web Development. Retrieved on 31st March 2013 from http://csrc.lse.ac.uk/asp/aspecis/20000053.pdf [5]. Transistor functionality [image] (2011). Retrieved 08th April 2013 on http://users.ece.gatech.edu/~alan/ECE3080/Lectures/ECE3080-L-0-Introduction.pdf [6]. Intel. (n.d.). Moore’s Law Inspires Intel Innovation. Retrieved 11th April 2013 from http://www.intel.com.au/content/www/au/en/silicon-innovations/moores-law-embedded-technology.html

You May Also Find These Documents Helpful

  • Powerful Essays

    BAE

    • 1989 Words
    • 7 Pages

    The process of requesting bid for the design and construction of the baggage handling system came a little too late because the PMT realized that to build an integrated system they needed to take responsibility for the project from the airlines, and this placed a lot of pressure on the project schedule that exposed the project to series of mistakes in it implementation.…

    • 1989 Words
    • 7 Pages
    Powerful Essays
  • Satisfactory Essays

    • This model is one of the best model to be used if the requirements and the goals are very clear even the large products can be developed very effectively. If the large projects are divided in to small separate projects and then are developed with waterfall model. Researcher’s confirms that the projects will be very organized and effective in terms of resources.…

    • 945 Words
    • 4 Pages
    Satisfactory Essays
  • Powerful Essays

    Abstract— During the process of software development, gathering requirement is the very imperative task. Both functional as well as non functional requirements play an important role in building the quality software. Little work has been done in the field of gathering the non functional requirements. To reflect the FRs and NFR’s properly, a solid architectural foundation is needed. Modeling is the best way to achieve such a goal, and Using UML tools can help to achieve the goal of eliciting functional as well as non functional requirements. We use UML models to represent FRs and NFRs of the system because UML has emerged as the industry standard for software modeling notations. This work provides the thorough and comprehensive work done in the field of eliciting non functional requirements. A new technique has been presented that helps in getting the non functional requirements right. This technique covers all the phases of requirement engineering and produces very valid results, as the goal of requirement engineering i.e.. Fulfilling the demands of stakeholder is completely satisfied.…

    • 3386 Words
    • 14 Pages
    Powerful Essays
  • Powerful Essays

    A city council developed a replacement payroll system believed that users had comprehensive knowledge of all the business requirements. But the current staff or IT team had participated in building the old system - they had no knowledge of how it was built. That leads to many errors and it cause project failure.…

    • 1090 Words
    • 5 Pages
    Powerful Essays
  • Powerful Essays

    Kanban in Software

    • 8626 Words
    • 35 Pages

    [29] W. W. Royce, “Managing the development of large software systems: Concepts and techniques,” in ICSE ’87: Proceedings of the 9th international conference on Software Engineering. Los Alamitos, CA, USA: IEEE Computer Society Press, 1987, pp. 328–338.…

    • 8626 Words
    • 35 Pages
    Powerful Essays
  • Good Essays

    In this essay I will compare two well-known and widely used methods of software development, the traditional Waterfall Method and the more recently established Agile Method. The Waterfall method is a structured, linear approach that breaks down the software development process, or life-cycle, into distinct stages. The Agile method is just as the name states, it is flexible and adaptable. It breaks the development process into smaller segments defined by deliverable goals, each segment runs through a complete software development life-cycle.…

    • 1381 Words
    • 6 Pages
    Good Essays
  • Powerful Essays

    thesis chapter 3

    • 4578 Words
    • 18 Pages

    The Waterfall Model shown in figure 2 consisted of six phases: (1) requirements; (2) analysis; (3) design; (4) coding; (5) testing and (6) acceptance. While the hardware development part, was done using the prototyping development model(http://en.wikipedia.org/wiki/waterfall).…

    • 4578 Words
    • 18 Pages
    Powerful Essays
  • Satisfactory Essays

    ◦ Prototyping ◦ Linear Sequential Model/Waterfall model Iterative and Incremental Development is at the heart of a cyclic software development process developed in response to the weaknesses of the waterfall model. It starts with an initial planning and ends with deployment with the cyclic interactions in between.…

    • 282 Words
    • 2 Pages
    Satisfactory Essays
  • Powerful Essays

    Top Management Visitor Appointment System (TMVAS) will implement the revised waterfall model approach of Software Development Life Cycle (SDLC). Bomarius et al., (2009) stated that Walter Royce’s article in 1970 is the first publication on the waterfall model. Waterfall model is seen flowing steadily downward resemble water cascading down a series of steps. In this approach, there are five phases involved that are requirements, design, implementation, testing and documentation. Figure 3.1 illustrates the revised waterfall model. Revised waterfall model being choose for TMVAS because once there is lack in any phases it can be correct easily. It can go back to earlier…

    • 1273 Words
    • 6 Pages
    Powerful Essays
  • Better Essays

    Conference Management

    • 2183 Words
    • 9 Pages

    Ö. Göl et al Quang Thai Tran received his Bachelor of Engineering in Computer Systems Engineering in 2004 from the University of South Australia (UniSA), Adelaide, Australia. Since graduation, he has worked as an Information Technologist at the UniSA. He is now studying for his MBA degree at the UniSA in Information and Communications Technology Management.…

    • 2183 Words
    • 9 Pages
    Better Essays
  • Powerful Essays

    software engineering

    • 3131 Words
    • 13 Pages

    Jump up ^ "Software engineering ... has recently emerged as a discipline in its own right." Sommerville, Ian (1985) [1982]. Software Engineering. Addison-Wesley. ISBN 0-201-14229-5…

    • 3131 Words
    • 13 Pages
    Powerful Essays
  • Powerful Essays

    At the stage of analysis, we had followed the waterfall Development Methodology. The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards though the phases of Conception, Initiation, Analysis, design, Construction, Testing and Maintenance.…

    • 5533 Words
    • 23 Pages
    Powerful Essays
  • Powerful Essays

    Protyping

    • 1580 Words
    • 7 Pages

    This lecture will examine the role of prototyping in Systems Development. It will describe what prototyping is, why it is used and how it may be applied in Systems Development Projects. It will establish approaches to evaluating a Prototype and finally it will discuss criteria for successful use of prototyping in a Systems Development Project.…

    • 1580 Words
    • 7 Pages
    Powerful Essays
  • Satisfactory Essays

    Sad Syllabus

    • 1586 Words
    • 7 Pages

    |design for producing logical methodologies for dealing with complexity in the development of information systems. The course approaches the development of information systems from a problem-solving perspective. This course builds upon concepts|…

    • 1586 Words
    • 7 Pages
    Satisfactory Essays