Assignment-1 Project Feasibility Study

Book Store System

1: The client for whom the work will be done.

The persons who want to buy books. A persons who want to buy book without going to bookstore that can be buy a book online through here.

2 : Visibility plan
Class diagram. Object diagram. Use-case diagram. Activity diagram.

3: A statement of the task to be undertaken.

Students can search the various books which are provided by the author to sell. Buyer can register by their mail id or buy a mobile number. Buyer can access their account by their id or by a mobile number. Buyer can buy also order book that cannot present in our library. Buyer can ask for any query regarding to books, payment, or any other information. Any publisher can upload their books in our system. Students also upload some material about special topic. Some books given free to buyer to read online and view some content of them.

4 : A preliminary requirements analysis.

Buyer info. Seller info. Visitor info. Price info. Buying system.

5 : Suggested deliverables.
Report &documentation. Presentation. Software copy in compact disk. User manual book. Training material.

6 : Process to be followed

Requirement & Analysis

Design

Coding

Testing

Maintenance

Requirement & Analysis Gethering all the requirements and analyst that requirements with in a week. Designing To construct different models with in a week. Coding After the designing phase coding part will be taken 1 month. Testing After the complition our coding work we are going to our next phase which is know as testing and it is completed after 1 and half month approximately. Maintenance Owner must maintain the site daily.

4 3.5 3 2.5 2 1.5 1 0.5 0 Requirement & Analysis Designing Coding Testing Maintenance Series 5 Series 4 Series 3 Series 2 Series 1

7 : Outline plan
Requirement Design Implementation Verification Maintenance

Percentage vs Weeks
120 100 80 60 40 20 0 1 2 3 4 5 6 7 8 9 10

Series 1

8: Risk Analysis
Three major risk categories have been identified: time, resource, and functionality. Time Risk: As course requirements specify that the project must be completed within one academic semester, any extensions are not possible. This introduces the risk that the system may not be completed with the full functionality the client wants the given timeframe of a semester. In this case, there is also a second risk of delayed implementation of the system if the client chooses to wait until the system is fully functional.

Resource Risks: Resource risks involve technologies the team has available for their use. Due to costs and other external contains, the team may not be able to obtain the needed or best resources to complete parts of the system. Functionality Risk: Functionality risks have to do with how the system works. Issues that fall under this category include developing a user interface that is not user-friendly or not well-liked by the client, or producing functions that have limited sustainability. The biggest risk comes from developing a system that does not do what the client wants it to do.

9 : Probable technical requirements

Developing Environment Front end: c# .net framework 4.0 Back end: SQL server 2005,MS access Working environment Platform: Windows 7 Server: windows 2005 server Hardware Requirement: 1 GB RAM 25 GB HDD Core 2 due