Software Development Concept
Software development life cycle (SDLC) is a set of several phases as under. Once the software passes through all these phases over a period of time, it becomes necessary to restart the software development afresh. That is why it is called as a cycle.
(a) Feasibility Study
In this curtain raiser phase, the developer tries to visualize all the subsequent phases and then tries to answer the question: Is it feasible?” This crucial phase has a decisive bearing on the project initiation and hence the developer aims at a sort of skimming through all the future phases to figure out probable handicaps and hindrances. Unless there are promising solutions to these anticipated hiccups and the complete project can be viewed as one complete, smooth activity, no green signal is given to the project. We provide more details on feasibility.
(b) Requirements Analysis
Now that the proposed system appears to be feasible, the next step is to understand neatly all the requirements of the would be users of that software. Unless all these user requirements are appreciated fully, the developers cannot design the software, let alone write the programs. The requirements collection is therefore a critical and foundational phase in the SDLC.
Typically the person who interacts with the users to get their requirements is called a ‘Systems Analyst’. She has to be well versed professional having multi-faculty skills in software development, analytical bend of mind, inter-personal communication skills and preferably working skills in the functional walk/subject matter to be computerized.
These requirements are gathered in the form of umpteen tidbits like how many reports users expect, what are the layouts and frequencies of such outputs what inputs go into the system and what are their respective formats and sources, what exactly takes place in the name of processing and what are all the intermediate recordings, calculations, authorizations, etc that decide the path of workflow and fate of an individual transaction, what happens if it is an exceptional case, how much of human intervention is needed, and many such points.
If we get back to out earlier example of the carpenter, user requirements could be quite limited like say inputs are going to be the dimensions and number of boxes to be produced as per order on hand and a single output that would give out the raw material requirements in terms of quantity of wooden planks needed for that order. However, in a complex application like banking, there may be hundreds of outputs that are worked out from several inputs coming from thousands of customers whose transaction types might be running into dozens.
Services: - Software Development Concept Homework | Software Development Concept Homework Help | Software Development Concept Homework Help Services | Live Software Development Concept Homework Help | Software Development Concept Homework Tutors | Online Software Development Concept Homework Help | Software Development Concept Tutors | Online Software Development Concept Tutors | Software Development Concept Homework Services | Software Development Concept