SOFTWARE DEVELOPMENT LIFE CYCLE

FEASIBILILTY ANALYSIS Feasibility study is done so that an ill-conceivedsystem is recognized early in definition phase. Duringsystem engineering, however, we concentrate ourattention on four primary areas of interest. Thisphase is really important as before starting with thereal work of building the system it was veryimportant to find out whether the idea thought ispossible or not.

Economic Feasibility: An evaluation of development cost weighted against the ultimateincome or benefit derived from the developedsystem.

Technical Feasibility: A study of function,performance and constraints that may affect theability to achieve an acceptable system.

Operational Feasibility: A study about theoperational aspects of the system.

ECONOMIC ANALYSIS

Among the most important information contained infeasibility study is Cost Benefit Analysis andassessment of the economic justification for acomputer based system project. Cost BenefitAnalysis delineates costs for the project developmentand weighs them against tangible and intangiblebenefits of a system. Cost Benefits Analysis iscomplicated by the criteria that vary with thecharacteristics of the system to be developed, therelative size of the project and the expected returnon investment desired as part of companys strategicplan. In addition, many benefits derived from acomputer-based system are intangible (e.g. betterdesign quality through iterative optimization,increased customer satisfaction throughprogrammable control etc.)As this is an in-houseproject for the company, to be used for its ownconvenience and also it is not that big a project. Soneither it requires a huge amount of money nor anycostly tools or infrastructure need to be set up for it. TECHNICAL ANALYSIS

During technical analysis, the technical merits of thesystem are studied and at the same time collectingadditional information about performance, reliability,maintainability and predictability. Technical analysis begins with an assessment of thetechnical viability of the proposed system.

What technologies are required to accomplishedsystem function and performance?

What new materials, methods, algorithms orprocesses are required and what is theirdevelopment risk?

How will these obtained from technical analysisform the basis for another go/nogo decision on thetest system? If the technical risk is severe, if models indicate

that the desired function can notbe achieved, if the pieces just wont fit togethersmoothly-its back to the drawing board.As the software is vary much economically feasible,then it is really important for it to be technically sound. The software will be build among:

MS SQL SERVER as Back End

ASP.NET as Front End

Operational Feasibility The project is operationally feasible. This project isbeing made for the convenience of the patients anddoctors only. This system will greatly reduce a hugeburden of doctors. So because of the above statedadvantages the users of the system will not bereluctant at all.SYSTEM ANALYSISINTRODUCTION:System analysis is the process of studying the businessprocessors and procedures, generally referred to asbusiness systems, to see how they can operate andwhether improvement is needed. This may involve examining data movement andstorage, machines and technology used in the system,programs that control the machines, people providinginputs, doing the processing and receiving the outputs. INVESTIGATION PHASE T h e i n v e s t i g a t i o n p h a s e i s a l s o k n o w n a s t h e f a c t - finding stage or the analysis of the current system. Thisi s a d e t a i l e d s t u d y c o n d u c t e d w i t h t h e p u r p o s e o f wanting to fully understand the existing system and toidentify the basic information requirements. Varioust e chniques may be used in factf i n d i n g a n d a l l f a c t obtained must be recorded.A thorough investigation was done in every effec

tedaspect when determining whether the purposed systemis feasible enough to be implemented. INVESTIGATIONAs it was essential for us to find out more about thepresent system, we used the following methods togather the information: 1. Observation: - Necessary to see the way the systemworks first hand. 2. 2 Document sampling: - These are all the documentsthat are used in the system. They are necessary to check all the data thatenters and leaves the system. 3 Questionnaires: - These were conducted to get viewsof the other employees who arecurrently employed in the system.

ANALYSIS OF THE INVESTIGATION Strengths of the System 1. No complex equipment: The equipment that is usedis very simple and no special skillshave to be mastered to be able tooperate the system. Therefore notraining is required for the employees. 2. Low cost: There is little money spent inmaintaining the present system otherthan buying the necessary officeequipment and the ledgers

Requirement And Feasibility Analysis

INTRODUCTION:What Is A Feasibility Study?

Prior to stating whether the system we have to developis feasible or not we believe that we should emphasizeon what is implied by the word Feasibility. Feasibilityis the measure of how beneficial or practical thedevelopment of the system will be to the organization.It is a preliminary survey for the systems investigation.It aims to provide information to facilitate a later in-depth investigation. The report produced at the end of the feasibility studycontains suggestions and reasoned arguments to helpmanagement decide whether to commit furtherresources to the proposed project.Within the scheduled duration we were assigned tostudy both the positive and negative aspects of thecurrent manual system, in which we have come up witha number of drawbacks that prevent the progress of the clinic if it is continued to function manually.Having gone through all measures of feasibility wereport to the management to figure out if theobjectives of the new system are met.For e.g. - Is the system within the budget allowed for it?

Compared to the semi-computerized system thechances of avoiding errors in a computerized system ismuch higher because the user need not stress himself unnecessarily resulting in recklessness. Unlike thesemi-computerized system there would be backup datafor all the information concerning the daily transactionsoccurred within the organization.If we are considering the performance and responsetime for each task, it is very much faster since there isless paper work to be completed. When entering datainto the system to relieve the user from additional workand typing incorrect data, the system provides optionssuch as combo boxes, check boxes, option buttons andetc. if the users type in incorrect data they would beinformed immediately about the error by the errordetection control.Another important fact to be regarded is the securitycontrol, which is handled by the system. Since dataregarding each student and the company isconfidential, security is a key issue. Information fallinginto the wrong hands could jeopardize the entire organization. Unlike in semi-computerized systems theproposed system offers adequate control to protect theorganization against fraud and embezzlement andguarantees the accuracy and security of data andinformation. This is handled by the system providingeach department and individuals with separate loginnames and passwords. The new system is more user-friendly, which enablesthe end-user to complete his/her work efficiently andaccurately with interest. After taking the above fact intoconsideration we can state the operating of theproposed system within the organization is feasible.In this phase of the feasibility study the following twomain topics

 Technical Performance Aspect Acceptance within the organization Technical performance aspect is explained in thetechnical feasibility report and there is no newinformation is needed in this to explain it again, but aS for the acceptance within the organization the followingpoints are important and those are explained accordingto the topics 1. Whether the system provides right information tothe right place.In the current system which is the semi computerizedsystem the information may be lost in the process of sending from one place to another. This is mainly dueto human interaction in the process of the transferringinformation from one place to ano

Software Requirement Specification The software requirement specification is producedat the culmination of the analysis task. Thefunction and performance allocated to software aspart of system engineering are refined byestablishing a complete information description, adetailed functional description, a representation of system behavior, an indication of performance requirement and design constraints appropriatevalidation criteria, and other information pertinentto requirement. The introduction to software requirementsspecification states the goals and objectives of thesoftware, describing it in the context of thecomputer based system. The Information Description provides a detaileddescription of the problem that the software mustsolve. Information content, flow and structure aredocumented.A description of each function required to solve theproblem is presented in the Functional Description.Validation Criteria is probably the most importantand ironically the most often neglected section of the software requirement specification.Software requirement specification can be used fordifferent purpose. Here are the major uses.not clearly understood by the developer. If this isthe case, a careful analysis involving muchinteraction with the user should be devoted to

reaching a clear statement of requirements, inorder to avoid possible misunderstandings.Sometimes, at the beginning of a project, even theuser has no clear idea of what exactly the desiredproduct is. Think for instance of user interface , auser with no previous experience with computerproducts may not appreciate the differencebetween , say menu driven interaction and acommand line interface. Even an exact formationof system functions and performance may bemissing an initial description produced by aninexperienced user.A statement of the requirements for theimplementation:Specifications are also used as a

reference pointduring product implementation. In fact, theultimate goal of the implementation is to build aproduct that needs specification. Thus theimplementers use specifications during design to make design decisions and during the verificationactivity to check that the implementation compileswith specifications.