Assumptions/Risk Assessment Assumptions support the base of the solution.

Assumptions include Library houses a certain minimum number of copies of the same book for s a k e o f many borrowers. Library uses original books/CDs. Library does not advise users to copy CDs/DVDs onto their computers. Library restricts the maximum number of borrowable items for different users. Library server runs a version of Windows operating system. Client systems support .NET Framework. User has basic computer knowledge and knows how to search/find information in theinternet. User has a decent internet speed to run the online solution. Functional Specification Initially when the solution is host in the server, administrator accounts are s e t u p . T h e s e administrators manage the server. First time users can carry on with simple search but thosewho want to borrow books need to sign-up for this facility. They can then sign-in anytime for searching, borrowing or returning books. They can also view their profile pages, history of their transactions Infrastructure Infrastructure plays an important role in this type of server-client computing. Both server andclient require a minimum amount of configuration to run the implementation. Server/Solution Platform Server must run a WINDOWS OS which supports IIS so that the website can be deployed.T h e s e r v e r m u s t a l s o b e c a p a b l e o f r u n n i n g V i s u a l w e b d e v e l o p e r a n d S Q L S e r v e r f o r database management. Client Platform Client system must run a windows operating system. It must run browsers which support.NET framework like Internet Explorer or Mozilla Firefox Modules A module is a logically separable part of a program. It is a program unit that is discrete andidentifiable with respect to compiling and loading. Partitioning a system in two modules isuseful only if the modules are solvable and modifiable. Separately a system is consideredmodular if it consists of discrete components such that each component supports a well-defined abstraction, and if a change to one component has a minimal impact on other component. Brief description of each of the 3 modules is given below.

a. Administrator Moduleb. Librarian Modulec.c. Students Module Administrator Module: In this module, all pages which are related to the Administrator means related to security andmaintenance of the portal and department are placed here. Creating Librarian Account. Modifying, Updating and deleting Librarian Accounts. Uploading and Unloading the Notice Board Material. Viewing & Updating Library Status. Viewing & Updating Students Details and Faculty Details Librarian Module: In this module, all pages which are related to Librarian are placed here.Viewing their Information and AccountAddingBooks News papersNew StudentViewingBooksStudents StatusBook StatuS ooksReference BooksUpdatingBooks News papersNew StudentDeletingBooks News papersNew Student Student Module: In this module, all pages which are related to Librarian are placed here.Viewing their Information and Account Registration Search for a book View profile View Library card StatuS ESTING PROCEDURE After completing every part of the software there is the need for software testing to prove thatthe module are functioning properly or not and it fulfills all requirement of the user. For this,the programmer use various type of software testing techniques and strategies. Software can be tested in one of two ways -: Black - Box Testing -: K n o w i n g t h e s p e c i f i e d f u n c t i o n t h a t a p r o d u c t h a s b e e n designed to perform, tests can be conducted that demonstrate each function is fullyoperational while at the same time searching for errors in each function. White Box Testing -:

K n o w i n g t h e i n t e r n a l w o r k i n g o f p r o d u c t , t e s t s c a n b e conducted to ensure that all gears mesh, that is internal operations are performedaccording to specification and internal component have been adequately exercised VALIDATION CHECK The main data, which is requested, is all the details about maintain Issue-Return Books,Add New Members, and Collection of Fines, Dynamic Search etc. Then we have to feedall these details to find out the users need.Details that are required are -:1 . W h i l e t h e member profile table maintains entry, it checks the Category N a m e , Organization, Email, Name, State, City, etc. for inserting only string data and inMember ID, Barcode, Phone, Mobile, etc. for inserting only number data.2.While maintaining Purchase-Order and Purchase-Order Received, in P.O.Number,Quantity, Price Per Unit, Total Price, Invoice Number, Quantity Ordered, Quan.Received, Sales Tax, Discount and Invoice Amt., we cant insert string data.3 . I n a m o u n t f i e l d c a n t a c c e p t o t h e r t h a n c u r r e n c y d a t a a n d w e c a n t u s e d e c i m a l point more than one time.4.In all the forms where I include data grids, we have to enter data first in text fields but after that we have to move into datagrids with TAB key, otherwise the datawill not be saved or deleted.5.Any entry can be edited by members if they have rights IMPLEMENTATION AND MAINTENANCE System Requirements to Run the Software: To run this project , user must have following tools and environments Software Requirements: Web Designing and Maintaining Web browser Computer-Based Training Multimedia Applications Data base server Hardware Requirements: Color monitor for good resolution Internet connectivity facility Microsoft compatible mouse Microsoft compatible keyboard

FUTURE SCOPE This application can be easily implemented under various situations. We can add new featuresas and when we require. Reusability is possible as and when require in this application. Thereis flexibility in all the modules. SOFTWARE SCOPE: Extensibility :This software is extendable in ways that its original developers may not expect. The following principles enhances extensibility like hide data structure, avoid traversing multiple links or methods, avoid case statements on object type and distinguish public and private operations. Reusability: Reusability is possible as and when require in this application. We can update it next version.Reusable software reduces design, coding and testing cost by amortizing effort over several designs.Reducing the amount of code also simplifies understanding, which increases the likelihood that thecode is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects. Understandability: A method is understandable if someone other than the creator of the method can understandthe code (as well as the creator after a time lapse). We use the method, which small andcoherent helps to accomplish this. Cost-effectiveness: Its cost is under the budget and make within given time period. It is desirable to aim for asystem with a minimum cost subject to the condition that it must satisfy the entirerequirement.Scope of this document is to put down the requirements, clearlyidentifying the informationneeded by the user, the source of the information and outputs expected from the system Introduction Situation Gone are the days when the librarian had to have his library log updated manually with help of his assistants.T h e t e d i o u s p r o c e s s o f u p d a t i n g t h e l o g , m a n u a l l y , a f t e r e v e r y t r a n s a c t i o n i s d y i n g o u t i n m o s t o f t h e libraries. This is with the advent of computerization in this field too.T h e n c a m e s p r e a d s h e e t s w h i c h u s e d t o r u n f o r p a g e s . E v e n t h e n i t w a s t h e d u t y o f t h e librarian/administrator to enter all details manually in the spreadsheet. She/he had to keep track of all itemsi n t h e l i b r a r y a n d u p d a t e t h e c o r r e s p o n d i n g r e c o r d s . T h e p e r s o n b o r r o w i n g t h e b o o k h a d t o g e t h i s verification card and get it updated every time he borrows/returns an item from/to library. Even this work of verifying the person and updating the card falls on the librarian or his assistant. Every now and then thelibrarian has to keep track of all the books and other items by checking the stocks (i.e. stocking). Solution This solution is developed using .NET technology which improves the accuracy of the information by leapsand bounds. This solution helps the administrator accomplish his tasks at ease. This solution is an onlinelibrary management system which lets users sign-up to the library initially and then sign-in every time theywant to find some item in the library. The user can also maintain and edit his profile details.It also lets administrators manage the library

from their desktop. They can monitor any item, its stock andother related information. A user can sign-in and search for items, borrow or reserve items if they are presentin the library. If not, user can request the librarian/administrator to get the book by furnishing all the details.As soon as a user reserves a book the library database gets updated automatically. This improves accuracyand leaves no user fooled about the status of availability of an item. All details of the user are stored in thedatabase which eases pressure on the administrator about defaulters. Defaulters can be blocked/removedfrom the library, by the administrator.The user need not visit the library every time to find an item; instead he/she can search items from his/her own PC/laptop. Reports can also be generated for individual items or for number of defaulters and thenumber of transactions for an item or by a user. They can also be generated in graphical form.An advantage of this solution is that a web browser which supports .net framework is enough to view theuser interface. This interface can be seen in any such system and hence makes it portable too enefits Accurate Information around the clock Information about the library database is accurate at any given point of time since its all automaticand updated after every transaction. Ease of access Users can find items, reserve book, change profile details, etc., from their homes as the librarystransactions are online. Maintenance is easy Managing the database is easy and so is its maintenance. It does not require much of care and goes onuntil it isnt affected due to heavy trafficking Sorting of data Data is stored in different databases and sorted into different tables to differentiate content and it caneasily converted into reports for presentations

micci_1001

/ 1

Download this Document for Free

System Development Life Cycle The Systems Development Life Cycle (SDLC) is a conceptual model used in projectmanagement that describes the stages involved in an information systemdevelopment project from an initial feasibility study through maintenance of thecompleted application. Various SDLC methodologies have been developed to guidethe processes involved including the waterfall model (the original SDLC method),rapid application development (RAD), joint application development (JAD), thefountain model and the spiral model. Mostly, several models are combined into somesort of hybrid methodology. Documentation is crucial regardless of the type of modelchosen or devised for any application, and is usually done in parallel with thedevelopment process. Some methods work better for specific types

of projects, butin the final analysis, the most important factor for the success of a project may behow closely particular plan was followed. The image below is the classic Waterfall model methodology, which is the first SDLC method and it describes the various phases involved in development. Briefly on different Phases: Feasibility The feasibility study is used to determine if the project should get the goahead. Ifthe project is to proceed, the feasibility study will produce a project plan and budgetestimates for the future stages of development. Requirement Analysis and Design Analysis gathers the requirements for the system. This stage includes a detailedstudy of the business needs of the organization. Options for changing the businessprocess may be considered. Design focuses on high level design like, what programsare needed and how are they going to interact, low-level design (how the individualprograms are going to work), interface design (what are the interfaces going to looklike) and data design (what data will be required). During these phases, the software's overall structure is defined. Analysis and Design are very crucial in thewhole development cycle. Any glitch in the design phase could be very expensive tosolve in the later stage of the software development. Much care is taken during thisphase. The logical system of the product is developed in this phase. Implementation In this phase the designs are translated into code. Computer programs are writtenusing a conventional programming language or an application generator.Programming tools like Compilers, Interpreters, Debuggers are used to generate thecode. Different high level programming languages like C, C++, Pascal, Java are usedfor coding. With respect to the type of application, the right programming languageis chosen. Testing In this phase the system is tested. Normally programs are written as a series ofindividual modules, these subject to separate and detailed test. The system is thentested as a whole. The separate modules are brought together and tested as acomplete system. The system is tested to ensure that interfaces between moduleswork (integration testing), the system works on the intended platform and with theexpected volume of data (volume testing) and that the system does what the userrequires (acceptance/beta testing). Maintenance Inevitably the system will need maintenance. Software will definitely undergo changeonce it is delivered to the customer. There are many reasons for the change. Changecould happen because of some unexpected input values into the system. In addition,the changes in the system could directly

affect the software operations. The softwareshould be developed to accommodate changes that could happen during the postimplementation period. The systems development life cycle is a project management technique that divides complexprojects into smaller, more easily managed segments or phases. Segmenting projects allowsmanagers to verify the successful completion of project phases before allocating resources tosubsequent phases. Software development projects typically include initiation, planning, design, development, testing, implementation, and maintenance phases. However, the phases may be divided differently depending on the organization involved. For example, initial project activities might be designated as request, requirements-definition, and planning phases, or initiation, concept-development, and planning phases. End users of the system under development should be involved in reviewing the output of each phase to ensure the system is being built to deliver the needed functionality. Note: Examiners should focus their assessments of development, acquisition, and maintenance activities on the effectiveness of an organizations project management techniques. Reviews should be centered on ensuring the depth, quality, and sophistication of a project management technique are commensurate with the characteristics and risks of the project under review. INITIATION PHASE Careful oversight is required to ensure projects support strategic business objectives and resources are effectively implemented into an organization's enterprise architecture. The initiation phase begins when an opportunity to add, improve, or correct a system is identified and formally requested through the presentation of a business case. The business case should, at a minimum, describe a proposals purpose, identify expected benefits, and explain how the proposed system supports one of the organizations business strategies. The business case should also identify alternative solutions and detail as many informational, functional, and

network requirements as possible. The presentation of a business case provides a point for managers to reject a proposal before they allocate resources to a formal feasibility study. When evaluating software development requests (and during subsequent feasibility and design analysis), management should consider input from all affected parties. Management should also closely evaluate the necessity of each requested functional requirement. A single software feature approved during the initiation phase can require several design documents and hundreds of lines of code. It can also increase testing, documentation, and support requirements. Therefore, the initial rejection of unnecessary features can significantly reduce the resources required to complete a project. If provisional approval to initiate a project is obtained, the request documentation serves as a starting point to conduct a more thorough feasibility study. Completing a feasibility study requires management to verify the accuracy of the preliminary assumptions and identify resource requirements in greater detail. Primary issues organizations should consider when compiling feasibility study support documentation include: Business Considerations: Strategic business and technology goals and objectives; Expected benefits measured against the value of current technology; Potential organizational changes regarding facilities or the addition/reduction of end users, technicians, or managers; Budget, scheduling, or personnel constraints; and Potential business, regulatory, or legal issues that could impact the feasibility of the project. Functional Requirements:

End-user functional requirements; Internal control and information security requirements;

Operating, database, and backup system requirements (type, capacity, performance); Connectivity requirements (stand-alone, Local Area Network, Wide Area Network, external); Network support requirements (number of potential users; type, volume, and frequency of data transfers); and Interface requirements (internal or external applications). Project Factors: Project management methodology; Risk management methodology; Estimated completion dates of projects and major project phases; and Estimated costs of projects and major project phases. Cost/Benefit Analysis: Expected useful life of the proposed product; Alternative solutions (buy vs. build); Nonrecurring project costs (personnel, hardware, software, and overhead); Recurring operational costs (personnel, maintenance, telecommunications, and overhead); Tangible benefits (increased revenues, decreased costs, return-oninvestments); and Intangible benefits (improved public opinions or more useful information). The feasibility support documentation should be compiled and submitted for senior management or board study. The feasibility study document should provide an overview of the proposed project and identify expected costs and benefits in terms of economic, technical, and operational feasibility. The document should also describe alternative solutions and include a recommendation for approval or rejection. The document should be reviewed and signed off on by all affected parties. If approved, management should use the feasibility study and support documentation to begin the planning phase. PLANNING PHASE

The planning phase is the most critical step in completing development, acquisition, and maintenance projects. Careful planning, particularly in the early stages of a project, is necessary to coordinate activities and manage project risks effectively. The depth and formality of project plans should be commensurate with the characteristics and risks of a given project. Project plans refine the information gathered during the initiation phase by further identifying the specific activities and resources required to complete a project. A critical part of a project managers job is to coordinate discussions between user, audit, security, design, development, and network personnel to identify and document as many functional, security, and network requirements as possible. Primary items organizations should address in formal project plans include: Project Overview Project overviews provide an outline of the project plan. Overviews shouldidentify the project, project sponsors, and project managers; and should describe project goals,background information, and development strategies. Roles and Responsibilities Project plans should define the primary responsibilities of key personnel, including project sponsors, managers, and team members. Additionally, project plans should identify the responsibilities of third-party vendors and internal audit, security, and network personnel. Communication Defined communication techniques enhance project efficiencies. Therefore, management should establish procedures for gathering and disseminating information. Standard report forms, defined reporting requirements, and established meeting schedules facilitate project communications. Management should establish acceptance criteria for each project phase. Management shouldalso establish appropriate review and approval procedures to ensure project teams completeall phase requirements before moving into subsequent phases. Defined Deliverables Clearly defined expectations are a prerequisite for successfully completing projects. Representatives from all departments involved in, or

affected by, a project should assist in defining realistic project objectives, accurate informational, functional, and interface requirements, and objective acceptance criteria. Control Requirements An essential part of the planning process involves designing and building automated control and security features into applications. Identifying all required features and exactly where they should be placed is not always possible during initial project phases. However, management should consider security and control issues throughout a projects life cycle and include those features in applications as soon as possible during a projects life cycle. Risk Management Managing risks is an important part of the project planning process. Organizations should establish procedures to ensure managers appropriately assess, monitor, and manage internal and external risks throughout a projects life cycle. The procedures should include risk acceptance, mitigation, and/or transfer strategies. External risks include issues such as vendor failures, regulatory changes, and natural disasters. Internal risks include items that affect budgets, such as inaccurate cost forecasting or changing functional requirements; scheduling difficulties, such as unexpected personnel changes or inaccurate development assumptions; and work flow challenges, such as weak communication or inexperienced project managers Change Management Personnel often request the addition or modification of functional requirements during software development projects. Although the addition or modification of requirements may be appropriate, standards should be in place to control changes in order to minimize disruptions to the development process. Project managers should establish cut-off dates after which they defer requested changes to subsequent versions. Additionally, representatives from the same departments involved in establishing requirements should be involved in evaluating and approving proposed changes. Large, complex, or

mission-critical projects should include formal change management procedures. Standards Project plans should reference applicable standards relating to project oversight activities, system controls, and quality assurance. Oversight standards should address project methodology selections, approval authorities, and risk management procedures. System controls standards should address functional, security, and automatedcontrol requirements. Quality assurance standards should address the validity of project assumptions, adherence to project standards, and testing of a products overall performance. Management should review, approve, and document deviations from established standards. Documentation Project plans should identify the type and level of documentation personnel must produce during each project phase. For instance, personnel should document project objectives, system requirements, and development strategies during the initiation phase. The documentation should be revised as needed throughout the project. For example, preliminary user, operator, and maintenance manuals created during the design phase should be revised during the development and testing phases, and finalized during the implementation phase. Scheduling Management should identify and schedule major project phases and the tasks to be completed within each phase. Due to the uncertainties involved with estimating project requirements, management should build flexibility into project schedules. However, the amount of flexibility built into schedules should decline as projects progress and requirements become Copy of System Development Life Cycle