درباره من
Engineering Homework Help: Systems Adequacy, Clarity
As the requirements capture is an intriguing exercise that absorbs the full attention, it is highly desirable to keep a track of some points continually throughout this phase.
(a) Adequacy: While the systems analyst focuses on one fact of the existing system at a time and delves into its depth, she has also bear in mind the overall perspective of the whole system.
There have been instances where a minutely studies system missed out on a couple of vital factors leading to the need for painful patching of software in its early stages. According to homework help online to prevent this, you must ensure a full coverage of the various sub-systems that form the system under study.
A classic instance of how a single missed-out functionality brings down the entire system’s usability can be found in an early car design that did not have a reverse gear! Something similar has happened in accounting systems that did not provide for adjustment entries with value dating, or inventory where pilferage could never be recorded, or in a missile trajectory system that did not incorporate a process for clock synchronization.
It therefore pays to sit back once in a while and review the sufficiency aspect of the whole exercise of the systems study. Needless to say, such reviews should be periodically carried out.
More: https://studydaddy.com/homeworks-answers
(b) Clarity: this relates to the certainty about the meaning of the documented facts and figures. As the issues in a systems study are at times quire complex and inter-dependent, it is necessary that ample words and the rest to arrest the exact meaning.
Lack of clarity may cause peculiar hassles of misinterpretation down the people chain that consists of designers, programmers, testers, etc. as user interaction is generally confined to systems analysts and the rest of the development team may not interact with users.
Clarity also has to be weighed against the need for elaborateness. It is human reluctance to read through pages of detailed description and one tends to ignore the particulars, when such niceties become voluminous. This has led to certain well defined diagramming techniques that we describe the subsequent aspects, where you will find a fitting application of the maxim – one picture is worth a thousand words.
(c) Common understanding: It is of utmost importance in a computerization project that both users and developers view the existing system (and later on, the design of the new system) in an exactly identical way. If any gap of understanding is not senses and rectified right away, it may cost very dearly as time passes by and the SDLC phases advance ahead. According to studydaddy.com this has been illustrated in a classic cartoon where a user desirous to procure a swing explains his requirements as ‘something hanging with a rope’ with which the designer produces a noose!
It is not just in a lighter vein, but there have been umpteen real life stories on how such misunderstandings spell doom. There is an example of a municipal corporation that was computerizing its property tax collection. In the course of discussions, a facility of paying an annual bill in two six-monthly installments was somehow missed out and which down the line resulted in the system denying acceptance of such installments.
More resources:
Engineering Homework Help: Structured Programming
Engineering Homework Help: Documentation, Sign Off
Engineering Homework Help: Output Forms Types
