Scribd
Upload
66 views6 pages

1.1 Goal and Objectives: The Main Objective Is To Build A Long Lasting

The document outlines plans for developing a supplier portal including goals, modules, estimates, requirements, schedule, team organization, and quality assurance. The main goal is to build relationships with suppliers through a customized portal providing secure access to applications and tools. Key modules include auctions, forums, messaging, directories, and interactions. Estimates are provided for each module with the full project estimated at 11,200 hours. The project is scheduled to be completed over 9 months with defined stages for requirements, design, programming, testing and acceptance.

Uploaded by

Mohit Talwar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
66 views6 pages

1.1 Goal and Objectives: The Main Objective Is To Build A Long Lasting

The document outlines plans for developing a supplier portal including goals, modules, estimates, requirements, schedule, team organization, and quality assurance. The main goal is to build relationships with suppliers through a customized portal providing secure access to applications and tools. Key modules include auctions, forums, messaging, directories, and interactions. Estimates are provided for each module with the full project estimated at 11,200 hours. The project is scheduled to be completed over 9 months with defined stages for requirements, design, programming, testing and acceptance.

Uploaded by

Mohit Talwar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

1. Introduction 1.

1 Goal and Objectives: The main objective is to build a long lasting relationship with all suppliers to ensure strong communication and support in all areas of our business. The Supplier Portal enables the next generation of business partner collaboration by providing customized, partner-specific access, services, applications and tools all delivered securely to the end user's desktop through the public internet. 1.2 General Requirements Role-based access (functions and layout depend on role) Shared homepage or workspace Integrated security User configurable Administrator configurable Peer-to-peer functionality

1.3 Proposed Modules Auction Module Forum Internal Messaging system Bulletin Board Directory of Companies Content Management Supplier Interaction Module Client Interaction Module Employee Interaction Module Transaction Module

2. Project Estimates 2.1 Estimation Techniques Assume that one has to deliver an end-to-end login module's functionality for an application. The time spent on the login functionality should include the corresponding time required for gathering the requirements, doing a requirement analysis, architecture inputs, form design, object/class design, implementing the business rules, data validation and storage, framework (i.e., code for login module's constants, enumerations, utilities), testing, debugging, deployment up to user acceptance, etc. Now, the estimator has to figure out how many man-hours it would take to complete the login module, keeping all these factors in mind. The sequence of work and dependencies should be considered as they do cause delays in completion. For example, form design should be done first (all the way up to acceptance by the customer), then object design (up to acceptance by the architect), followed by coding (for business rules, calculations, and data validations), internal testing, and user acceptance testing. A wise estimator would always take support from other people to understand the scope of work to do a given task.

Login Module Auction Module Bulletin Board

1400 Hrs 500 Hrs 500 Hrs

Directory of Companies Content Management Internal Messaging system Supplier Interaction Module Client Interaction Module Transaction module Employee Module Total

500 Hrs 500 Hrs 500 Hrs 1800 Hrs 1800 Hrs 2300 Hrs 1400 Hrs 11200 Hrs

2.2 Hardware Requirements


Hardware Web Server Application Server Database Reporting Engine Email/Messaging Server Portal Server Directory Services, Security, identity management, Audit, ETL, any other. Specification Windows Server 2003, 8 GB RAM, 1 TB HDD Websphere Application Server Oracle 10 G Cognos 8 Business Intelligence SMTP Server, Microsoft Exchange Services Windows Server 2003, 8 GB RAM, 1 TB HDD

2.3 Software Requirements Software Operating system Specification Windows Vista/7/8 OS Enterprise Edition on all operating system in Organization, 2 GB RAM, 120 GB HDD IDE XML Editor QTP Load-Runner QTP 8.0 Performance Testing Tools Visual Studio 8

3. Project Schedule Stage Planning Deliverables Quality Assurance Plan Project Plan Milestone Date 1/1/2013

Requirement Definition

Draft Requirement 2/1/2013 specification Draft Design Specification Project Test Plan

Requirement Specification Milestone Design (Functional and system) Draft Training Plan Program and Database specification Design spec Final Coding System testing Testing and Integration Plan, Results Maintenance plan Acceptance Test Report 3/1/2013

Programming

6/1/2012

Integration and Testing

7/1/2013

Installation and Acceptance

8/1/2013

4. Project Team Organization

Project Manager

Technical Lead

Tech Architect

Software Engineer

Test Engineer/ Quality executive

5. Tracking and Control Mechanism 5.1 Quality Assurance Mechanisms Tight Change Management Extensive before implementation Design using Rapid Prototyping Close Contact with Clients, meeting every two weeks and regular email contacts 5.2 Change Management and Control For changes affect the user experiences we will have to notify all clients For changes that do not affect the user experiences we will notify a client representative Due the size of the team, internal control panel will be used. One member of the team suggests a change; it will need to be approved by the other two members Formal version numbering will be used. All version changes must be documented in a common document accessible to all team members before a new version number can be released. Version number will be structured as follows: <Major Release>.<Minor Release><Bug fix>

You might also like