VEE model
This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "VEE_model".

For other uses, see V-Model (software development).
The V-model of the Systems Engineering Process.1

The V-Model (or VEE model) is a systems development model designed to simplify the understanding of the complexity associated with developing systems.234 In systems engineering it is used to define a uniform procedure for product or project development.

--219.79.50.215 (talk) 17:28, 7 January 2009 (UTC)--219.79.50.215 (talk) 17:28, 7 January 2009 (UTC)--219.79.50.215 (talk) 17:28, 7 January 2009 (UTC)== Overview == The V-model is a graphical representation of the systems development lifecycle. It summarizes the main steps to be taken in conjunction with the corresponding deliverables within computerized system validation framework.

The VEE is a process that represents the sequence of steps in a project life cycle development. It describes the activities and results that have to be produced during product. The left side of the VEE represents the decomposition of requirements, and creation of system specifications. The right side of the V represents integration of parts and their verification. 56347 V stands for "Verification and Validation" 77

content

Contents

V Model topics

Systems engineering and verification.8

Systems Engineering and verification

The Systems Engineering Process (SEP) provides a path for improving the cost effectiveness of complex systems as experienced by the system owner over the entire life of the system, from conception to retirement.1

It involved early and comprehensive identification of goals, a concept of operations that describes user needs and the operating environment, thorough and testable system requirements, detailed design, implementation, rigorous acceptance testing of the implemented system to ensure it meets the stated requirements (system verification), measuring its effectiveness in addressing goals (system validation), on-going operation and maintenance, system upgrades over time, and eventual retirement.1347

The process emphasizes requirements-driven design and testing. All design elements and acceptance tests must be traceable to one or more system requirements and every requirement must be addressed by at least one design element and acceptance test. Such rigor ensures nothing is done unnecessarily and everything that is necessary is accomplished.13

The specification stream

The specification stream mainly consists of:

  • User Requirement Specifications
  • Functional Specifications
  • Design Specifications

The testing stream generally consists of:

  • Installation Qualification (IQ)
  • Operational Qualification (OQ)
  • Performance Qualification (PQ)

The development stream can consist (depending on the system type and the development scope) in customization, configuration or coding..

Applications

Off-Core alternatives (illustrating upward and downward iterations and Time and Maturity dimension). Source - K. Forsberg and H. Mooz 200437

The V-model is used to regulate the software development process within the German federal administration. Nowadays it is still the standard for German federal administration and defence projects, as well as software developers within in the region.

The concept of the V-Model was developed simultaneously, but independently, in Germany and in the United States in the late 1980s. The US V-Model, as documented in the 1991 proceedings for the National Council on Systems Engineering (NCOSE; now INCOSE as of 1995),7 was developed for satellite systems involving hardware, software, and human interaction. It has now found wide-spread application in commercial as well as defence programs. Its primary use is in and Project Management34 throughout the project lifecycle.

One fundamental characteristic of the US V-Model is that time and maturity move from left to right and one cannot move back in time. All iteration is along a vertical line to higher or lower levels in the system hierarchy, as shown in the figure.347 This has proven to be an important aspect of the model. The expansion of the model to a dual-Vee concept is treated in reference 3.

As the V-model is publicly available many companies also use it. In project management it is a method comparable to PRINCE2 and describes methods for project management as well as methods for system development. The V-Model while rigid in process, can be very flexible in application, especially as it pertains to the scope outside of the realm of the System Development Lifecycle normal parameters.

See also

== References ==szzxczxczxcz

  1. ^ a b c d Clarus Concept of Operations. Publication No. FHWA-JPO-05-072, Federal Highway Administration (FHWA), 2005
  2. ^ "Systems Engineering for Intelligent Transportation Systems" pp 10. US Dept. of Transportation. Retrieved on 2007-06-09.
  3. ^ a b c d e f g h Forsberg, K., Mooz, H., Cotterman, H. Visualizing Project Management, 3rd edition, John Wiley and Sons, New York, NY, 2005. Pages 108-116, 242-248, 341-360.
  4. ^ a b c d e International Council On Systems Engineering (INCOSE), Systems Engineering Handbook Version 3.1, August 2007, pages 3.3 to 3.8
  5. ^ Forsberg, K., Mooz, H.. "System Engineering for Faster, Cheaper, Better". Center of Systems Management.
  6. ^ "The SE VEE". SEOR, George Mason University. Retrieved on 2007-05-26.
  7. ^ a b c d e Forsberg, K. and Mooz, H., "The Relationship of Systems Engineering to the Project Cycle," First Annual Symposium of the National Council On Systems Engineering (NCOSE), October 1991
  8. ^ Systems Engineering Fundamentals. Defense Acquisition University Press, 2001.

== External links ==xzzxzvzvzv

Sister project Wikimedia Commons has media related to: V-models
v • d • e
Systems engineering
Fields
System Engineering Process
Concepts
Tools
Systems engineers
Related fields
© jGames.co.uk 2007 (some content from Wikipedia under GDL ) !-- ValueClick Media 468x60 and 728x90 Banner CODE for jgames.co.uk -->
Your Ad Here