Requirements Specification and System Development Life Cycle
Compare and Contrast
Even though unambiguous and understandable cover the same thought of clarity of message, they can still be contrasted. This is because, unambiguous weighs a thought in one dimension so as to create a single lane of thought thus closing chances of a thought having any another interpretation (Zielczynski, 2008). It is mostly brought about by acronyms that have not been defined, incomplete command or a misplaced word. Understandable on the other hand means that a requirement should use correct grammar written in a uniform style. Additionally, must or may should be replaced by shall (Zielczynski, 2008).
Complete defines the total inclusion of every needed component and condition likely to occur, such that no addition is required on the system (Zielczynski, 2008). Furthermore, for a requirement to be complete, it should have adequate criteria. On the contrary, concise refers to provision of a large-sum amount of information comprehensively and in brief words that are simple and clear (Zielczynski, 2008). Moreover, both refer to provision of adequate information to the system.
Correct means that the function is accurate, with facts that are true, and without errors(Zielczynski, 2008). Modifiable means that the function is prone to being changed in form according to the requirements by containing one element that can be traceable and not having a requirement that gets expressed once with minimal chances of overlapping with another (Zielczynski, 2008). Both try to gauge the accuracy of the function to the specifications.
SDLC
A standard is a term used at the University of Kansas to define the least number of the needed phases and thoughts needed for the development and implementation of newly developed software and system( Ks 66045, n.d).
Standards have several uses such as: providing lowest level requirements for the works of developing the application (GO-ITS, 2007). Secondly, it provides a wide measure for making sure that the methodology used in development of an application goes hand in hand with its standard (GO-ITS, 2007). Thirdly, it outlines major features of a lifecycle methodology in addition to providing direction for a generic. Additionally, they intensify an application’s quality by suitable commenting and creating standardized labeling conventions (GO-ITS, 2007).
References
Zielczynski, Peter (2008). Requirements Management Using IBM® Rational® RequisitePro®. informIT the trusted technology learning source, Retrieved from http://www.informit.com/articles/article.aspx?p=1152528&seqNum=4
KS 66045, Lawrence (n.d). Systems Development Life Cycle (SDLC) Standard. INFORMATION TECHNOLOGY POLICY, Retrieved from http://policy.ku.edu/IT/systems-development-life-cycle-standard
GO-ITS (2007). Application Development Standard: Standards for SDLC. Information & Technology Standards, Retrieved from dr6j45jk9xcmk.cloudfront.net/documents/1890/go-its-54-application-development-standards-for.pdf