Escolar Documentos
Profissional Documentos
Cultura Documentos
Standards Documentation Standards Documentation should have elements like cover page, table of contents, headers, footers and other useful information. The cover page shall include the following information: Organization Name, Project Title and Document Title. A header shall be on all pages from the second page to the last page of the document indicating Project Title and Document Title. A footer shall be included on all pages from the second page to the last page of the document indicating Confidential if needed and page number. Indentation should be used to emphasize the body of a control statement such as a loop or a select statement. Three to four spaces shall be used to indent and tabs shall not be used for indentation purposes. Generally, every program must include one line of comment for every five lines of code. Alterations to requirements document must be permitted by the project manager. Designed programs name Special mathematical operations Timer Set text flush left and numbers flush right. A maximum of 40-60 characters per line of text.
Coding Standards
Risk Assessment
RISK #1: The project manager fails to plan and manage resources required for achieving goals because of some inevitable circumstance. Likelihood of risk: Medium probability of risk Potential impact on the project: This risk may lead to budget overruns, time overruns or both, or at most, to the failure of completing the project. Ways to address this risk: It is dire to have a full understanding of the systems that will be used to improve the project, and the project manager needs to certify the weaknesses of the development environment. Likewise, an effective project controlling and monitoring should be formed to enrich project performance thru the project life cycle. In cases of inevitable situations, proper site investigation should be done to ensure that all site conditions are noted in the design and apply value management that could be used to find the best cost effective options in addressing such situations. RISK #2: The team members are not so familiar with the technology and may not have the appropriate skills and knowledge about the system. Likelihood of risk: Medium probability of risk Potential impact on the project: The time to complete the tasks will be delayed. Ways to address this risk: Additional training through mentoring and hands-on instruction with a company trainer can be conducted. Aside from that, providing a written training manual that contains specific instructions and reference information will be a valuable resource for the new employee and will hasten his or her success. RISK #3: There may be loss or damage to operational capabilities caused by problems with premises, facilities, services or equipment. Likelihood of risk: Low probability of risk Potential impact on the project: The risk may suspend the completion of the system. Ways to address risk: It is very important to set up proper inspection regime of routine, operational and annual inspections on premises or facilities. Routine inspections are important, cost the least but are frequently ignored. Training someone, on how to do routine inspections can be an advantage. Also, ensure that repairs and maintenance as recommended by inspections are carried out as required.
Requirement Definition
Functional Requirements 1. Internet Usage Tracker 1.1. The system will record the amount of internet traffic that a customer uses. 1.2. The system will take note of internet caf location whether branch 1 or branch. 1.3. The system will record the time used by the customer. 1.4. The system will create a record of the internet speed, internet services used and internet sites visited by a certain registered customer. 2. Log-in log-off Internet access 2.1. The system will ask the customer options whether to set a certain time (minutes or hours) logged in or to manually logoff his account anytime. 2.2. If the customer only chooses for a certain time to be logged in, the system will automatically log off the customers account after such time.The system will let the administrator automatically set log customers off after X minutes. 3. Customer Printing Management 3.1. The system will provide customer with the use of the caf printers, automatically crediting each page printed to their account. 4. Customer Account and Billing Rates Management 4.1. The system will provide client information like credit card information and billing address. 4.2. The system will also supply information like internet usage by bandwidth used and internet usage per time period. 5. Reporting 5.1. The system will allow the client to log-in, and view the status of their account. 5.2. The system will show a report of the internet sales by customer home address, internet sales by caf location, internet traffic usage and daily sales. Non-Functional Requirements 1. Operational 1.1. The system has to be online 24 hours a day, 7 days a week. 1.2. The system will have an independent browser based application, allowing customers with all types of operating systems to connect provided they have proper hardware. 1.3. The system should link to the laser printers and copiers wirelessly.
2. Performance 2.1. The system will show data screens with no noticeable pauses. 2.2. Data requests will be loaded within 3 seconds. 3. Security 3.1. The system will protect all confidential data by transmitting it on a network using an encrypted connection. 3.2. No employee can access any customers personal account. 3.3. Only the owner and customer can approve changes in customer accounts. 4. Cultural and Political 4.1. Customers private information is protected in accordance with the Data Privacy Act of 2012.
Staffing Plan
Role Project Manager Description Allocates resources, shapes priorities, coordinates interactions with customers and users, and generally keeps the project team focused on the right goal Acts as a technical designer for the iNets infrastructure as well as the core network and all desktop technologies Designs new systems including process flow, user interface, reports, and security procedures Installs, customizes, and maintains the operating system, and also installs or upgrades products that run on the system Assigned To Gleir
Infrastructure Analyst
Kathleen
Systems Analyst
Johanna
Programmer
Precyl
Task ID 1 1.1 1.1.1 1.2 1.2.1 1.2.2 1.3 1.3.1 1.3.2 1.3.3 1.4 1.4.1 2 2.1 2.1.1 2.1.2 2.1.3 2.2 2.2.1 2.2.2
Task Name Analysis Determine business requirements Customer and employee interviews Create use cases Create use case diagrams Create use case descriptions Model processes Data flow diagram State chart diagrams Sequence diagrams Model data Network Model Design Design interface User interface layout Navigation Diagram Screen prototypes Database design Database ERD Data Dictionary
Dependency
Status Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open
Gleir
Kathleen Kathleen
1.1.3
Johanna Johanna
3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.2 3.2.1 3.2.2 3.2.3 3.2.3.1 3.2.3.2 3.2.3.3 3.3 3.3.1 3.3.2 3.3.3
Implementation Code programs and Test Unit test plans Module test plans Code programs Unit test plan results Individually test modules Install system Integration tests and results Help/tutorial Deployment Guides System administrator User Standalone Installation Post-implementation System Documentation User Manuals ID sheet and installation CD
3/7 3/7 3/7 3/7 3/12 3/12 3/31 4/4 4/4 4/4 4/9 4/9 4/9 4/9 4/13 4/13 4/13 4/13
4/16 4/3 3/11 3/11 3/30 3/16 4/3 4/8 4/8 4/8 4/12 4/12 4/12 4/12 4/16 4/16 4/13 4/13 2.2.1.3 2.2.1.3 3.3.1.3.1.1 3.3.1.3.1.2 3.3.1.3.1.1 3.3.1.3.1.3 3.3.1.3.1.5
Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open
Kathleen Precyl
3.3.2.3.2.1 3.3.2.3.2.2
3.3.2.3.2.3