Professional Documents
Culture Documents
Louis, Missouri
and has a loyal customer base throughout the Midwest. The Widget Company attributes its marketplace success to innovative procedures and customer responsiveness. Widget is an early adopter of technology innovations that have been thoroughly proven in the industry.
Proof of Certification A.
CMMI Level 5 Company ISO 9001-14001
B. Organization Details
Directory of Companies
This is a listing of all registered associates of the B2B portal either by business category or by alphabetical order. An advanced search engine tool is incorporated in order to find a company based on data provided.
Content Management
To manage the learning documents, informative documents etc on a common organized platform
Transaction Module
Elaborate Messaging System allows a participant of the B2B portal send and receive messages from other participants and the company.
Employee Module
Information Management system for Employee providing features like Dashboard etc.
Solution Information
Technical Documentation:
Hardware Web Server Application Server Database Reporting Engine Specification Windows Server 2003, 8 GB RAM, 1 TB HDD Websphere Application Server Oracle 10 G Cognos 8 Business Intelligence
Email/Messaging Server Portal Server Directory Services, Security, identity management, Audit, ETL, any other.
SMTP Server, Microsoft Exchange Services Windows Server 2003, 8 GB RAM, 1 TB HDD
Specification Windows Vista/7/8 OS Enterprise Edition on all operating system in Organization, 2 GB RAM, 120 GB HDD
Visual Studio 8
Assumptions
Proposal takes into assumption the streamlined business process at client site which are to be automated using Portal System.
Terms of Agreement
1. In consideration of the charges to be paid by the Client as specified in the Proposal, Company will provide the Services. Where the Proposal indicates that a functional specification will be written that specification will supersede the Proposal. Both Company and Client will agree, in writing, any material changes to the Software or Services. 2. Where the parties agree that there should be acceptance testing of the Software, then after installation of the Software, the Client shall deliver test data and results expected to be achieved and the Client shall accept the Software immediately after the Software has correctly processed the test data by achieving the expected results. The Software shall not be deemed to
have incorrectly processed such test data by reason of any failure to provide any facility or function not specified in the Proposal or in any agreed functional specification. Repeat tests shall be undertaken at our discretion.
Project Plan
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.
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.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
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
7/1/2013
8/1/2013
Project Manager
Technical Lead
Tech Architect
Software Engineer
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>