240 likes | 397 Views
Software process models. Name: Wassim Jamal Salem ID: 120070570 Name : Mohammed Khalid Alkhalily ID: 120080016. Waterfall model.
E N D
Software process models Name:Wassim Jamal Salem ID:120070570 Name:Mohammed Khalid Alkhalily ID:120080016
Waterfall model In this model the life cycle of moving gradually Step 1 - to step 5 This model is characterized by simplicity, so it is easier for the developer to clarify how the work on the project for a client (who does not know a lot of making software), and the remaining phases of work , And this was the form the basis of the work of many was heading for a long time, such as the U.S. Department of Defense, and derived from many of the most complex models.
Advantages of Waterfall Model • The waterfall model is the oldest and most widely used model in the field of software development. There are certain advantages of the waterfall model, which causes it to be the most widely used model as yet. Some of them can be listed as under .
Advantages of Waterfall Model Needless to mention, it is a linear model and of course, linear models are the most simple to be implemented . The amount of resources required to implement this model is very minimal. One great advantage of the waterfall model is that documentation is produced at every stage of the waterfall model development. This makes the understanding of the product designing procedure simpler. After every major stage of software coding, testing is done to check the correct running of the code
Disadvantages of Waterfall Model The question that must be bothering you now is that with so many advantages at hand, what could be the possible disadvantages of the waterfall model. Well, there are some disadvantages of this widely accepted model too. Let us look at a few of them.
Disadvantages of Waterfall Model Ironically, the biggest disadvantage of the waterfall model is one of its greatest advantages. You cannot go back, if the design phase has gone wrong, things can get very complicated in the implementation phase> Many a times, it happens that the client is not very clear of what he exactly wants from the software. Any changes that he mentions in between may cause a lot of confusion. Small changes or errors that arise in the completed software may cause a lot of problem
Disadvantages of Waterfall Model • The greatest disadvantage of the waterfall model is that until the final stage of the development cycle is complete, a working model of the software does not lie in the hands of the client. Thus, he is hardly in a position to mention if what has been designed is exactly what he had asked for what has been designed is exactly what he had asked for • The waterfall model, as already mentioned, is of course the most widely used model. There are various versions of the same, which allow some waterfall model phases to overlap or feedback to be taken after each phase, which make designing the software a lot more simpler. So this, in short, was all about waterfall model advantages and disadvantages. In spite of the disadvantages, the many advantages of this model ensure that it remains one of the most popular models used in the field of software development.
Spiral model Model represents the development of processes in the form of a spiral instead of following the sequence of the phases of the system with reference inversely for improvement. The throat of each snail one stage of the process, there are no fixed stages to determine the specifications of the system or the development, selection episodes in the snail on what is needed, and are risk assessment, analysis and resolved during the process. In the first quarter of snail is setting goals and alternatives and constraints, either in the second quarter are evaluating alternatives and the definition and risk analysis. The development is in the third quarter and makes sure the next stage of a product, and in the fourth quarter are planning the second phase.
Advantages of spiral Model Estimates (i.e. budget, schedule, etc.) become more realistic as work progresses, because important issues are discovered earlier. It is more able to cope with the (nearly inevitable) changes that software development generally entails. Software engineers (who can get restless with protracted design processes) can get their hands in and start working on a project earlier.
Disadvantages of spiral Model Highly customized limiting re-usability. Applied differently for each application. Risk of not meeting budget or schedule .
Mix between waterfall & Spiral(case study): • I am a professional data warehousing consultant with a background in SEI/CMMI, Six Sigma, and TQM principles. I utilize many different types of development paradigms from RAD/JAD to Waterfall & Spiral hybrids. At the end of the day I can mix and match what you need from the SDLC to architect the right data warehouse for your needs.
Cont. • Our Mission… • Faith Based Integrity Minded Coporate IT Consulting, bettering the world one project at a time.
Cont. • Our Goals… • To bring hope and success to broken, failing, or struggling data warehouses, to provide the world with faith based innovative designs, architectures and implementation best practices that will engage your team, improve efficiency, and reduce overall costs of your data warehousing projects.
Mix between waterfall & Spiral: • By UML • Introduction: • Unified Modeling Language provides a set of best practices, engineering expertise, which proved successful in modeling large and complex systems, an important part of the development-oriented extensions of the software processes and software development.
Cont. • Not the Unified Modeling Language methodology to build or software design and development. • Not linked to the Unified Modeling Language methodology or methods of production software, and can be employed such language on the various processes code, regardless of the methodology.
Cont. • Almouhp modeling language consists of four basic layers of each layer in turn are divided into classes based on a sub-divided into abstraction:
1-User Objects Layer: • Is the surface layer of the public used by those who deal with the Unified Modeling Language, consisting of nine plans major addition to the objects and tools to help a class, the most visible and description, and explain the written language of this class, and is used here is intended to user language and not the end-user of the software or product code, The first layer includes the following nine charts.
2-Model Layer: • And be in the carry-over from the first analysis, contains the concepts of the subject of analysis as understand the system in general or a domain analysis or the area of the system, and uses this layer analyzer system during its work before the maturity of the system or the idea of clarity and characterization of the lower layer of the first user.
3-Meta Model Layer: • Concerned with this class of concepts related to the language of the Unified Modeling as a concept product and phenomenon, and the data type, abstraction, patterns and other aspects of the language, a layer that describes what is going on in the form and consists of three packages, namely: a package base package elements behavioral management pack form.
4-Meta meta model layer: • Layer does not concern most of the systems analysts and they constitute the basis of language and interested in writing the Unified Modeling language, and of interest to developers tools such as Unified Modeling Language software, which automates the drawings and paints.