EYE OPTICAL MANAGEMENT SYSTEM

SOFTWARE ENGINEERING LAB

SLOT: L13+ L14
VL2023240505809

SUBMITTED BY:
ARUN.U
21BCE3187
 Assessment – I

1. Explain Analysis and Identification of the suitable process models to

project?

Project Overview:
The Eye Optical Management System aims to streamline the lens
manufacturing and management processes in optical shops. The system
includes modules such as registration and login, lens data management,
inventory control, quality control, order processing, and reporting & analytics.
Stake holders:
1.Customers - Customers seeking eyewear and optical services are stakeholders
in the sense that the system should cater to their needs for easy navigation,
quick order processing, and accurate information about available products.
2.Shop staff - Employees working in the optical shop, such as salespersons,
optometrists, and administrative staff, are crucial stakeholders. They will
interact with the system daily and rely on it for tasks like order processing,
inventory updates, and customer management.
3.Suppliers - Suppliers providing lenses, frames, and other optical products to
the shop are stakeholders. The system can assist in managing relationships with
suppliers, tracking orders, and maintaining optimal inventory levels.
4.Optical shop management - They are primary stakeholders who are directly
involved in the operation and management of the optical shop. They would be
interested in the system for efficient inventory management, order processing,
and overall business operations.
Process model for the project:
The optical industry experiences dynamic changes in trends, technologies,
and customer preferences. A process model that allows for flexibility and
adaptability to evolving requirements is crucial. The Eye Optical Management
System comprises various modules, and stakeholders include optical shop
owners, staff, and customers. Effective collaboration and continuous feedback
from stakeholders are essential for the success of the project.
The nature of the system demands a focus on risk management, ensuring that
potential issues are identified and addressed promptly. Precision is vital,
considering the need for accurate lens data, inventory control, and quality
assurance. Providing a user-friendly interface and ensuring customer
satisfaction are paramount. The process model should facilitate user
involvement at various stages, allowing stakeholders to provide feedback and
contribute to the system's usability.

Considering the aforementioned factors, I consider the most suitable process

model for the Eye Optical Management System is the Iterative and Incremental
Development Model for the following reasons:
• Flexibility and Adaptability: The Iterative and Incremental Development
Model allows for the incremental delivery of the system, making it well-
suited for a project with evolving requirements. Each iteration can
address specific modules, adapting to changes in the optical industry.
• Continuous Stakeholder Involvement: Stakeholder involvement is crucial
for a project like the Eye Optical Management System. Iterative
development allows stakeholders, including optical shop owners and
staff, to provide feedback at each iteration, ensuring that the system
aligns with their needs.
• Risk Management: The iterative nature of the model facilitates ongoing
risk management. Potential issues can be identified early in the
development process, reducing the likelihood of major setbacks and
ensuring the system's stability.
• Usability and Customer Satisfaction: The model allows for the early
delivery of partial functionalities, providing stakeholders with a tangible
product to assess and provide feedback. This promotes customer
satisfaction and ensures that the system meets usability expectations.
Hence, The Iterative and Incremental Development Model is identified as
the most suitable process model for the Eye Optical Management System
for me. Its flexibility, continuous stakeholder involvement, focus on risk
management, and support for evolving requirements make it an effective
approach for the successful development of the system in the dynamic
optical industry.
2. Implement a Work Break-down Structure (Process Based, Product Based,
Geographic
Based and Role Based) and Estimations for project
Simple Workflow model:

Estimations:
Project Duration:
Total Duration: 6 months
Phases:
1. Initiation and Planning:
Duration: 1 month
• Define project objectives and scope
• Identify stakeholders and their requirements
• Formulate project team and roles
• Develop a detailed project plan and timeline
• Assess potential risks and mitigation strategies
2. Requirements Analysis and Design:
Duration: 1 months
• Gather and analyze system requirements
• Define user stories and use cases
• Document functional and non-functional requirements
• Create system architecture and design
• Develop UI/UX wireframes and prototypes
• Specify database structure and schema
3. Implementation:
Duration: 1 month
• Develop registration and login modules
• Implement lens data management
• Build inventory control functionalities
• Integrate quality control measures
• Develop order processing features
• Implement reporting & analytics

4. Testing:
Duration: 1 months
• Conduct unit testing for individual modules
• Perform integration testing
• Conduct system-wide testing
• Execute user acceptance testing (UAT)
5. Deployment and Training:
Duration: 2 months

• Roll out the system in a controlled environment

• Address any issues from the deployment phase
• Provide user training and support
6. Maintenance and Updates:
Duration: Ongoing (post-deployment)
• Implement ongoing maintenance procedures
• Release patches and updates as needed
• Provide continuous user support
Resource Allocation:
1. Project Manager:
Dedicated throughout the project for coordination and communication.
2. System Analyst:
Concentrated effort during the Requirements Analysis and Design phase.
3. UI/UX Designer:
Active during the Requirements Analysis and Design phase.
4. Developers:
Engaged in the Implementation phase.
5. Quality Assurance (QA) Team:
Involved during the Testing phase.
6. Deployment Team:
Active during the Deployment and Training phase.