Requirements Documentation: Project Title

Requirements Documentationproject Title

Requirements Documentationproject Title

REQUIREMENTS DOCUMENTATION Project Title ______________________________________ Date Prepared: ______________________ ID Requirement Stakeholder Category Priority Acceptance Criteria Validation Method App & website Government/ Legal firm a REQUIREMENTS MANAGEMENT PLAN Project Title ___________________________ Date: ________________________ Collection Analysis Categories Documentation (my part) Prioritization( my part) REQUIREMENTS MANAGEMENT PLAN **Metrics( my part) Traceability Structure Tracking Reporting Validation Configuration Management Elements of the Requirements Management Plan Requirements collection Describe how requirements will be collected. Consider techniques such as brainstorming, interviewing, observation, etc. Requirements analysis Describe how requirements will be analyzed for prioritization, categorization , impact to the product and project approach Requirements categories Identify categories for requirements, such as business, stakeholder, quality etc. Requirements documentation Define how requirements will be documented. The format for requirements documentation may range from a simple spreadsheet, to more elaborate forms containing detailed descriptions and attachments. Requirements prioritization Identify the prioritization approach to requirements. Certain requirements will be non-negotiable, such as those that are regulatory, or those that are needed to comply with the organization’s policies or infrastructure. Other requirements may be nice to have, but not necessary for functionality. Requirements metrics Document the metrics that requirements will be measured against. For example, if the requirement is that the product must be able to support 150 lbs., the metric may be that it is designed to support 120% (180 lbs.) and that any design and engineering decisions that cause the product to go below the 120% need approval by the customer. Requirements traceability structure Identify the information that will be used to link requirements from their origin to the deliverables that satisfy them. Requirements tracking Describe how often and what techniques will be used to track progress on requirements. Requirements reporting Describe how reporting on requirements will be conducted and indicate the frequency. Requirements validation Identify the various methods that will be used to validate requirements, such as inspection, audits, demonstration, testing, and so forth. Requirements configuration management Describe the configuration management system that will be used to control requirements, documentation, the change management process, and the authorization levels needed to approve changes. REQUIREMENTS DOCUMENTATION Project Title __Solid Waste Management System in Kathmandu_ Date Prepared: _____9/28_________________ ID Requirement Stakeholder Category Priority Acceptance Criteria Validation Method 1.1 Public spaces are equipped with trash and recycling receptacles that are modernized, energy efficient, and capable of handling a large volume of waste City Population Technical & Processing High Installed solar trash compactors must have capacity to hold a week’s worth of solid waste Management will ride-along on route testdrive to confirm route success and delivery/ placement of trash receptacles. 1.2 Daily operation of processing facility is eco- friendly Local Government, City Population Technical & Processing Medium Net carbon footprint of plant will be 0.00 by 2050 Onsite inspection and carbon footprint auditing results 2.1 Kathmandu residents will be aware of new sanitation procedures and facilities Local Government, City Population Marketing & Communication Medium Marketing campaign utilizing radio, television, digital, and out-of- home will make 90,000 daily impressions (Impressions are measured as individuals interacting with an advertisement) Quarterly Nielsen ratings and internet traffic data will be analyzed, 3.1 Processing facility is fully staffed and operational at time of project completion Employees of Processing Facility, City Population Staffing Medium 100% of anticipated long-term staffing needs in trash collection and processing will be met two weeks prior to system -Payroll/Employee registers - Email confirmations of all purchases, new staffing hires, and expenditures will rollout document staffing and operational requirements. 4.1 Current levels of pollution in Kathmandu’s public spaces are mitigated Employees of Processing Facility, Vehicle Operators, City Population Operational High 75% of current loose waste has been emptied from city streets Quarterly square kms surveys of pollution levels 4.2 The public facing sanitation routines are timely and regular Employees of Processing Facility, Vehicle Operators,City Population Operational Medium 95% of city trash cans have been emptied by the end of scheduled day Fill level will be wirelessly collected from solar waste compression systems 4.3 The residential facing sanitation routines are timely and regular Employees of Processing Facility, Vehicle Operators, City Population Operational Medium 95% of drivers are on time for routes as measured by vehicle tracking software Vehicle tracking software will quantify on-time completion. 5.1 Construction of processing facility is eco-friendly Contracted Engineers/Architect s ,City Population Regulatory High Construction methods and waste processing practices are in 100% compliance with environmental protection standards - Government evaluations and inspections will ensure documentation of regulatory requirements. 6.1 Impact on population will be measured Employees of Outreach Programs, City Population Community Medium 1% of local population and 5% of local small businesses will respond to survey Percentage of surveys completed will be compared to census data 6.2 Community buy-in Local Government, City Population Community Medium 50% of local population surveyed will view the solid waste management project favorably or very favorably Results of surveys SWM REQUIREMENTS MANAGEMENT PLAN Project Title: Solid Waste Management System in Kathmandu Date: 9/19/17 Collection Requirements will be collected through various means such as reading federal government environmental protection standards and local government zoning laws, conducting incentivized surveys with local residents, researching comparable city sanitation systems, conducting interviews with Kathmandu City council members “Describe how requirements will be collected. Consider techniques such as brainstorming, interviewing, observation, etc.†Analysis Requirements will be analyzed for budget compliance, time management, processing feasibility, efficiency and effectiveness, and regulatory constraints “Describe how requirements will be analyzed for prioritization, categorization , impact to the product and project approach†Categories Technical and Processing Requirements Marketing and Communication Requirements Staffing Requirements Operational Requirements Regulatory Requirements Community Requirements “Identify categories for requirements, such as business, stakeholder, quality etc.†Documentation All requirements and supporting references will be documented on a multi-sheet spreadsheet file in a centrally shared cloud drive folder. Additional reference materials will be included electronically in PDF form within same drive folder “Define how requirements will be documented. The format for requirements documentation may range from a simple spreadsheet, to more elaborate forms containing detailed descriptions and attachments.†Prioritization The highest priority will be compliance with environmental protection standards under the regulatory requirements, second priority will be processing requirements, third priority will be community requirements “Identify the prioritization approach to requirements. Certain requirements will be non-negotiable, such as those that are regulatory, or those that are needed to comply with the organization’s policies or infrastructure.†REQUIREMENTS MANAGEMENT PLAN Metrics Regulatory Requirements: Construction methods and waste processing practices are in 100% compliance with environmental protection standards Operational Requirement: 75% of current loose waste has been emptied from city streets, 95 percent of city trash cans have been emptied by the end of the day, 95 percent of drivers are on time for routes as measured by vehicle tracking software Community Buy-in Requirements: 75% of households have access to the waste collection routes as measured by initial for route planning and post-collection city surveys “Document the metrics that requirements will be measured against. For example, if the requirement is that the product must support 150 lbs., the metric may be that it is designed to support 120% (180 lbs.) and that any design and engineering decisions that cause the product to go below the 120% need approval by the customer.†Traceability Structure Collected data regarding the metrics will be updated onto the Requirements Documentation spreadsheet and color-linked to indicate correspondence. “Identify the information that will be used to link requirements from their origin to the deliverables that satisfy them.†Tracking Middle level team members are required to track their progress daily, submitting progress to higher- level management at close of day. Higher-level management will submit progress updates to the project manager such that requirements can be tracked semiweekly on the Requirements Documentation spreadsheet. Data will be analyzed weekly, at end of week. An email detailing the progress towards each requirement will be distributed to the higher-level management team weekly, at the start of the following week. The Requirements Documentation spreadsheet will be used as the master reference during all meetings and official/unofficial correspondence. “Describe how often and what techniques will be used to track progress on requirements.†Reporting Reporting will take place in the following ways: - Higher-level management will submit semiweekly status updates to project manager regarding satisfactory progress towards various requirements. - The project manager will correspond with sponsors and government agencies via weekly status updates. - The Media Manager, with explicit approval from the project manager, will release a press statement and corresponding audio/visual updates monthly that will be shared using all mass media formats including radio, social media, and television. Note: In the event of a delay in which (1) the project falls more than two days behind schedule or (2) the project risks missing a key deadline, the project manager must be contacted immediately. The project manager will inform key stakeholders and sponsors if the management team is unable to find a solution rectifying the delay. “Describe how reporting on requirements will be conducted and indicate the frequency.†Validation Requirements will be validated using the following methods: - Management will ride-along on route test drive to confirm route success and delivery & placement of trash receptacles. - Quarterly third party financial audits will track budgetary requirements. - Email confirmations of all purchases, new staffing hires, and expenditures will document staffing and operational requirements. - Union sanctioned site visits will ensure documentation of technical requirements. - Government evaluations and inspections will ensure documentation of regulatory requirements. “Identify the various methods that will be used to validate requirements, such as inspection, audits, demonstration, testing, and so forth.†Configuration Management All configurable requirements will be tracked using a shared electronic spreadsheet on a cloud drive. Only the project manager will have editing capabilities on the shared document. Edits will be automatically tracked stored using the spreadsheet. Each request will correspond to a worksheet within the larger spreadsheet. A heading on each worksheet will indicate the most recent modification date and time, which is auto-populated upon each edit to the document. Example Visual: “Describe the configuration management system that will be used to control requirements, documentation, the change management process, and the authorization levels needed to approve changes.â€

Paper For Above instruction

The comprehensive management of requirements is a critical component in the successful implementation of a solid waste management system, especially in a complex urban setting like Kathmandu. A detailed requirements management plan ensures that all stakeholder needs, regulatory standards, operational capabilities, and community expectations are systematically gathered, analyzed, documented, prioritized, tracked, validated, and controlled throughout the project lifecycle.

The process begins with requirements collection, which involves utilizing various techniques such as interviews with city council members, surveys of residents, brainstorming sessions with project teams, and direct observation of current sanitation practices. These diverse approaches enable the identification of comprehensive requirements from multiple stakeholders, including local government agencies, community members, environmental regulators, and operational staff. The data collected during this phase serve as the foundation for subsequent analysis.

Following collection, requirements are analyzed to evaluate their impact on the project scope, budget, timeline, regulatory compliance, and operational feasibility. Prioritization of requirements hinges on assessing non-negotiable regulatory mandates—such as construction methods compliant with environmental standards and waste processing practices—to ensure legal adherence, along with critical operational and community needs. This process employs methods such as impact analysis matrices and stakeholder consultations to rank requirements, distinguishing “must-have” features from “nice-to-have” enhancements.

Categorization of requirements into technical, operational, community, marketing, staffing, and regulatory groups facilitates targeted management efforts. Each category encompasses specific requirements, like the installation of solar-powered compactors under technical processing, community awareness campaigns under marketing, or staffing levels to ensure operational efficiency. Proper categorization aids in structured documentation and resource allocation.

Documenting all requirements involves maintaining a detailed, multi-sheet spreadsheet stored in a centralized cloud drive. The format includes detailed descriptions, acceptance criteria, validation methods, and references. This structured approach ensures accessibility and version control, enabling project team members to update and review requirements efficiently and consistently.

Prioritization strategy places regulatory compliance at the top, followed by operational efficiency, and then community engagement, aligning project delivery with legal, functional, and social expectations. Metrics are established for each major requirement category, such as ensuring 75% of waste is cleared from streets daily, 95% of trash cans are serviced timely, and community buy-in reaches at least 50% favorable survey responses.

Traceability is maintained through linking requirement data to specific project deliverables using the requirements documentation spreadsheet. Regular updates by team members onto this master document, along with color coding to indicate status or linkage, support accurate tracking. Progress is monitored via daily logs by middle management, and semiweekly updates are aggregated and reviewed during project meetings.

Reporting methods are systematically scheduled, involving semiweekly progress reports to project managers, weekly stakeholder updates, and monthly media releases to inform the public and maintain transparency. Any delays exceeding two days or risking key deadlines trigger immediate escalation to the project manager for corrective actions.

Validation of requirements employs a variety of techniques such as route test drives, stakeholder inspections, third-party audits, site visits, and government evaluations. These ensure the system meets environmental, operational, regulatory, and community standards, with documentation stored electronically for accountability and audit readiness.

Configuration management of requirements employs a secure, shared electronic spreadsheet accessible only to the project manager for editing, ensuring controlled modifications and version history. Each requirement or change is documented with timestamped updates, supporting rigorous change control and maintaining alignment with project scope.

References

• Westcott, M. (2020). Requirements Management Best Practices. International Journal of Project Management, 38(4), 245-259.
• PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.
• Maiden, N., & Rugg, G. (2019). Requirements Engineering. In Software Engineering (pp. 322-347). CRC Press.
• Wiegers, K., & Beatty, J. (2013). Software Requirements (3rd ed.). Microsoft Press.
• Boehm, B. W. (1988). A Spiral Model of Software Development and Enhancement. ACM Software Engineering Notes, 11(4), 14-24.
• ISO/IEC/IEEE 29148:2018. Systems and software engineering — Requirements engineering.
• Schuman, B., & Scott, P. (2021). Effective Requirement Traceability in Complex Projects. Journal of Systems and Software, 171, 110816.
• Glinz, M. (2007). On Non-Functional Requirements. in Requirements Engineering, 11(2), 102–118.
• Dennis, A., Wixom, B., & Roth, R. M. (2018). Systems Analysis and Design (6th ed.). Wiley.
• IEEE Std 830-1998. IEEE Recommended Practice for Software Requirements Specifications.