SPM

Prompt

You are an expert **Project Management and Software Engineering academic assistant**. Your task is to complete my university lab assignment and create a professional **Microsoft Word (.docx) file** that is ready for submission. ## Assignment Topic **Project Charter — Online Library Management System** ## Lab Tasks You must complete ALL of the following: 1. Create a **Project Charter** for an Online Library Management System. 2. Write at least **4 measurable project objectives**. 3. Identify at least **5 stakeholders**. 4. List at least **6 major project deliverables**. 5. Identify at least **4 assumptions** and **4 constraints**. 6. Identify at least **5 initial project risks**. 7. Define at least **6 items in scope** and **4 items out of scope**. 8. Write at least **5 acceptance criteria** for the proposed system. 9. Create and save the complete assignment as a **Microsoft Word (.docx)** document. --- # 1. Project Context Assume the proposed system is a web-based **Online Library Management System** for a university/college library. The system should allow students and library staff to manage common library activities digitally, such as: * User registration/login * Searching and browsing books * Viewing book availability * Borrowing/returning books * Managing due dates * Tracking borrowed books * Managing books and categories * Managing users * Calculating overdue fines * Generating basic library reports Do not make the project unnecessarily complex. Keep it realistic for a **university-level Software Engineering project**. --- # 2. Required Project Charter Sections Create a complete and professional Project Charter containing, at minimum: ### A. Project Information Include: * Project Title * Project Type * Project Sponsor * Project Manager * Organization * Proposed Start Date * Proposed End Date * Project Purpose * Project Description Use reasonable assumptions where information is not provided. Clearly label them as assumptions rather than pretending they were supplied. ### B. Project Purpose / Business Need Explain: * Why the library needs the system * Problems with a manual/traditional library process * How the proposed system addresses those problems * Expected organizational benefits Keep this section concise but meaningful. ### C. Measurable Project Objectives Provide **at least 4 SMART-style objectives**. Each objective should be: * Specific * Measurable * Achievable * Relevant * Time-bound Avoid vague objectives such as "make the system good." Use measurable targets where appropriate, for example: * response time * user registration success * search accuracy/functionality * system availability * reduction in manual processing * completion deadline Present the objectives in a professional table with columns such as: | # | Objective | Measurement/Target | Deadline | ### D. Stakeholders Identify **at least 5 stakeholders**. Possible stakeholders include: * Students * Librarians * Library Administrator * University Management * Project Manager * Development Team * IT/System Administrator For each stakeholder, explain: * Role * Interest in the project * Main expectations/responsibilities Use a table. ### E. Major Deliverables Provide **at least 6 major deliverables**. Examples may include: * Project Charter * Requirements Specification * System Design * Database Design * Developed Web Application * Testing Documentation * User Documentation * Deployment/Final System * Final Project Report Do not simply list them. Briefly describe each deliverable. Use a table. ### F. Assumptions Provide **at least 4 realistic assumptions**. Examples: * Users have access to the internet/local university network. * Library staff will provide required book and user data. * Required development tools are available. * Stakeholders will provide feedback during development. Make sure assumptions are genuinely things assumed to be true for planning purposes. ### G. Constraints Provide **at least 4 realistic constraints**. Consider: * Limited project time * Limited budget * Limited development team * Available technology/infrastructure * Academic project deadline * Data/privacy limitations Clearly distinguish constraints from assumptions. ### H. Initial Project Risks Identify **at least 5 initial risks**. For each risk include: * Risk ID * Risk Description * Probability * Impact * Risk Level * Mitigation/Response Use realistic risks such as: * Requirement changes * Development delays * Data loss * Security vulnerabilities * Server/infrastructure problems * Insufficient stakeholder feedback * Integration problems Do not invent absurd or irrelevant risks. ### I. Project Scope #### In Scope Provide **at least 6 specific items**. Examples: * User authentication * Book search * Book availability * Borrowing/return management * User management * Book/catalog management * Fine calculation * Basic reports #### Out of Scope Provide **at least 4 specific items**. Examples: * Mobile application * Online payment gateway * AI-based book recommendations * Integration with external libraries * Advanced biometric authentication Make the scope boundaries clear enough that a reviewer can understand what the project will and will not deliver. ### J. Acceptance Criteria Provide **at least 5 measurable acceptance criteria**. The criteria should describe conditions that must be satisfied before the system is accepted. Examples: * Authorized users can successfully log in. * Users can search books by defined search fields. * The system correctly displays book availability. * Borrowing and returning transactions are recorded correctly. * The system calculates overdue fines according to defined rules. * Unauthorized users cannot access administrative functions. * Required reports can be generated successfully. Make acceptance criteria **testable and measurable**, not subjective. Use a table: | # | Acceptance Criterion | Verification Method | --- # 3. Quality Requirements The final assignment must: * Be academically appropriate for a university Software Engineering course. * Use clear and professional English. * Avoid unnecessary jargon. * Avoid overly complicated enterprise-level features. * Maintain consistency between objectives, scope, deliverables, risks, stakeholders, and acceptance criteria. * Ensure every required task is explicitly addressed. * Use realistic assumptions rather than fabricated facts. * Do not leave placeholders such as "[Name]", "[Date]", or "[Insert Here]" unless absolutely necessary. * If personal information is required but unavailable, use neutral labels such as "Student" or "Project Manager" rather than inventing my personal details. --- # 4. Document Structure Create the Word document with the following structure: **Title Page** * Project Charter * Online Library Management System * Course/Lab Assignment * Prepared By * Date Then: 1. Introduction 2. Project Information 3. Project Purpose and Business Need 4. Project Description 5. Project Objectives 6. Stakeholder Identification 7. Major Deliverables 8. Assumptions 9. Constraints 10. Initial Project Risks 11. Project Scope * 11.1 In Scope * 11.2 Out of Scope 12. Acceptance Criteria 13. Project Success Considerations 14. Conclusion The required lab tasks must be clearly identifiable within these sections. --- # 5. Microsoft Word Formatting Create an actual **.docx file**, not just text. Use professional academic formatting: * A4 page size * Normal professional margins * Clear title page * Heading 1 / Heading 2 styles * Consistent font throughout * Professional tables * Table headers clearly distinguishable * Page numbers * Header/footer where appropriate * Proper spacing between sections * Bulleted lists where appropriate * No excessive decoration * No unnecessary colors * No broken tables * No text overflowing outside page boundaries Add a **Table of Contents** if technically possible. Make the document visually clean and suitable for university submission. --- # 6. Validation Before Saving Before creating the final file, perform a checklist-based quality review. Verify that: * [ ] Project Charter is complete. * [ ] At least 4 measurable objectives are included. * [ ] At least 5 stakeholders are identified. * [ ] At least 6 deliverables are included. * [ ] At least 4 assumptions are included. * [ ] At least 4 constraints are included. * [ ] At least 5 risks are included. * [ ] At least 6 in-scope items are included. * [ ] At least 4 out-of-scope items are included. * [ ] At least 5 acceptance criteria are included. * [ ] Acceptance criteria are testable. * [ ] Objectives are measurable. * [ ] Risks contain probability, impact, and mitigation. * [ ] Scope is consistent with the proposed system. * [ ] There are no contradictory statements. * [ ] There are no missing sections. * [ ] Grammar and spelling are correct. * [ ] Tables are readable. * [ ] The final document opens correctly as a Microsoft Word file. If any requirement is missing, correct it before saving the final document. --- # 7. Final Deliverable Create and save the completed document as: **Online_Library_Management_System_Project_Charter.docx** After creating the file: 1. Verify that the file exists. 2. Verify that it can be opened/read. 3. Report the final filename. 4. Provide the downloadable file to me. 5. Give me a very short summary of what was included. Do not merely provide the assignment text in the chat. **The primary deliverable must be the completed Microsoft Word (.docx) file.**