Difference between revisions of "Prototype (glossary)"
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023") |
|||
| (15 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <blockquote>''(1) '''Prototype - hardware''' - ''A specification-compliant production readiness demonstration model developed under engineering supervision that represents what manufacturing should replicate. All design engineering and production engineering must be complete, and the assembly must be under configuration control. | + | <blockquote>''(1) '''Prototype - hardware''' - ''A specification-compliant production readiness demonstration model developed under engineering supervision that represents what manufacturing should replicate. All design engineering and production engineering must be complete, and the assembly must be under configuration control.'' (Fairley 2009, p 74-75), (Forsberg, Mooz, Cotterman 2005, p 432)</blockquote> |
<blockquote>''(2) '''Prototype - software''' - A term currently with multiple meanings. A “rapid prototype” is usually a software requirements demonstration model, which provides a simulated representation of the software functionality and operator interface. The model facilitates early buyer-developer agreement on the design approach. A software prototype may also be a technical demonstration model. Except with “Evolutionary Prototypes,” the code is usually discarded once the model has served its purpose.'' (Forsberg, Mooz, Cotterman 2005, p 432)</blockquote> | <blockquote>''(2) '''Prototype - software''' - A term currently with multiple meanings. A “rapid prototype” is usually a software requirements demonstration model, which provides a simulated representation of the software functionality and operator interface. The model facilitates early buyer-developer agreement on the design approach. A software prototype may also be a technical demonstration model. Except with “Evolutionary Prototypes,” the code is usually discarded once the model has served its purpose.'' (Forsberg, Mooz, Cotterman 2005, p 432)</blockquote> | ||
| Line 5: | Line 5: | ||
<blockquote>''(3) '''Prototype - software''' - Software prototypes are constructed to investigate a situation or to evaluate a proposed approach to solving a technical problem. ... When building a prototype, we keep the knowledge we have gained but we do not use the code in the deliverable version of the system'' (Fairley 2009, p 74-75)</blockquote> | <blockquote>''(3) '''Prototype - software''' - Software prototypes are constructed to investigate a situation or to evaluate a proposed approach to solving a technical problem. ... When building a prototype, we keep the knowledge we have gained but we do not use the code in the deliverable version of the system'' (Fairley 2009, p 74-75)</blockquote> | ||
| − | === | + | ===Sources=== |
| − | (1) and ( | + | (1) and (2) Forsberg, K., H. Mooz, H. Cotterman. 2005. ''[[Visualizing Project Management]]'', 3rd Ed., John Wiley and Sons. |
| − | (3) Fairley, R. 2009. ''[[Managing and Leading Software Projects]]''. Hobken, NJ, USA: John Wiley & Sons. | + | (1) and (3) Fairley, R. 2009. ''[[Managing and Leading Software Projects]]''. Hobken, NJ, USA: John Wiley & Sons. |
===Discussion=== | ===Discussion=== | ||
| Line 14: | Line 14: | ||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| − | + | <center>'''SEBoK v. 2.9, released 20 November 2023'''</center> | |
Revision as of 22:25, 18 November 2023
(1) Prototype - hardware - A specification-compliant production readiness demonstration model developed under engineering supervision that represents what manufacturing should replicate. All design engineering and production engineering must be complete, and the assembly must be under configuration control. (Fairley 2009, p 74-75), (Forsberg, Mooz, Cotterman 2005, p 432)
(2) Prototype - software - A term currently with multiple meanings. A “rapid prototype” is usually a software requirements demonstration model, which provides a simulated representation of the software functionality and operator interface. The model facilitates early buyer-developer agreement on the design approach. A software prototype may also be a technical demonstration model. Except with “Evolutionary Prototypes,” the code is usually discarded once the model has served its purpose. (Forsberg, Mooz, Cotterman 2005, p 432)
(3) Prototype - software - Software prototypes are constructed to investigate a situation or to evaluate a proposed approach to solving a technical problem. ... When building a prototype, we keep the knowledge we have gained but we do not use the code in the deliverable version of the system (Fairley 2009, p 74-75)
Sources
(1) and (2) Forsberg, K., H. Mooz, H. Cotterman. 2005. Visualizing Project Management, 3rd Ed., John Wiley and Sons.
(1) and (3) Fairley, R. 2009. Managing and Leading Software Projects. Hobken, NJ, USA: John Wiley & Sons.
Discussion
None.