Scribd
Upload
2 views2 pages

Practical

The document outlines the software configuration management (SCM) objects for a PG Management System project. Key objects include source code artifacts, configuration files, database schemas, documentation, design assets, test artifacts, deployment scripts, and change requests. Each category is detailed with specific examples relevant to the project.

Uploaded by

neharathod1203
Copyright
© All Rights Reserved
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
2 views2 pages

Practical

The document outlines the software configuration management (SCM) objects for a PG Management System project. Key objects include source code artifacts, configuration files, database schemas, documentation, design assets, test artifacts, deployment scripts, and change requests. Each category is detailed with specific examples relevant to the project.

Uploaded by

neharathod1203
Copyright
© All Rights Reserved
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

Practical-06

6. Identify the objects for SCM in your project.


 SCM Objects in PG Management System
1. Source Code Artifacts
 Frontend files: HTML, CSS, JavaScript, React components
 Backend files: [Link]/[Link] modules, routing logic, helper
functions
 API endpoints: RESTful services for tenant management, billing,
room allocation
2. Configuration Files
 .env files for environment-specific variables (e.g., DB credentials,
API keys)

 package. Json and package-lock. Json for dependency tracking

 Webpack or Babel config files (if used)


3. Database Schemas and Seed Data
 MongoDB collection schemas (e.g., tenants, rooms, payments)

 Initial seed data for testing or deployment

 Migration scripts (if schema evolves)


4. Documentation
 Requirements documents: The Software Requirements Specification
(SRS) that defines the system's functions.
 Design documents: The High-Level Design (HLD) and Low-Level
Design (LLD) documents that outline the system's architecture and
modules.
 User manuals: Guides for administrators, PG owners, and tenants.
 Test plans and reports: Documents detailing testing procedures,
cases, and results.
5. Design and UI Assets
 Wireframes, mockups, and UI/UX design files

 Logo and branding assets

 CSS themes or style guides


6. Test Artifacts
 Unit and integration test scripts

 Test data files

 Test reports and coverage summaries


7. Deployment and Build Scripts
 Docker files or deployment YAMLs (if containerized)

 CI/CD pipeline configurations (e.g., GitHub Actions, Jenkins)

 Build artifacts and release notes


8. Change Requests and Audit Logs
 Version history of code and documents

 Change request records (e.g., feature additions, bug fixes)

 Audit trails for who changed what and when

You might also like