Software engineering project guidelines

1. Software engineering
project guidelines
SANA SAEED

2. Pharmacy management system
Front end
 Generic process framework for software engineering encompasses five
activities:
 Communication
 Planning
 Modeling
 Construction
 Deployment

3. Pharmacy management system
Front end:
 In software design, front end is the part of software system that deals with
users.
 A “front end” application is one the application user interact with directly.
Back end:
 Back end is the part that processes the input from the front end.
 A “back end” application or program serve indirectly in support of the
front end services.

4. User interface

5. Continued
 This system will do the following:
 Store medicine data
 Search medicine data effectively
 Generate report on medicine
 Prepare bill for the medicine
 Changing login, password

6. Communication
 Before starting technical work, its important to communicate with
stakeholder.
 The intent is to understand stakeholders’ objectives for the project and to
gather requirements that help define software features and functions.
 Example: pharmacy management system
 User friendly application for pharmacist.
 Application help to manage all section of pharmacy like medicine
management and billing which improve processing efficiency.

7. Continued
 Application must deal with automate task of maintaining bills.
 Data stored about the medicines safely as well as fast searching, delete,
and update of medicines.
 The pharmacy management system must be easy to use so the user can do
pharmacy actions without ambiguities.
Objective of the project:
 To design a system that can keep track of the user.
 To design a system that is useful for handling medicines
 To design a system that is much better than manual data recording system

8. Planning
 The main objective of software project planning is to create a detail plan
for a successful software project.
 Software project plan:
 defines the software engineering work by describing the technical tasks to
be conducted.
 the risks that are likely
 the resources that will be required
 the work products to be produced, and a work schedule

9. Example: pharmacy management
system
 Technical tasks:
1. Requirements Analysis and Specification
 Conduct meetings with stakeholders (pharmacists, managers, etc.) to
gather and document system requirements.
 Create a detailed requirements specification document, including
functional and non-functional requirements.

10. Continued
2. System Design
 Design the overall architecture of the Pharmacy Management System.
 Create a database schema for storing pharmacy-related data (products,
customers, prescriptions, etc.).
 Design the user interface for different user roles (pharmacists, cashiers,
managers).
 Plan for security measures to protect sensitive data.
 Choose the technology stack (programming languages, frameworks,
databases, etc.).

11. Continued
3. Database Development
 Implement the database schema.
 Set up data validation and integrity constraints.
 Create scripts for data migration and seeding initial data.
Identifying risks:
 Risk: Unforeseen technical issues, such as software bugs or platform
compatibility problems, can delay the project.

12. Continued
 Software Development Resources:
 Integrated Development Environment (IDE):
 Choose an IDE suitable for your programming language. Some popular options
include:
 Visual Studio Code: A versatile and free code editor.
 Database Management System (DBMS):
 Select a DBMS to store and manage pharmacy data. Common options include:
 MySQL: An open-source relational database.
 Programming Languages and Frameworks:
 Depending on your project requirements, choose suitable programming
languages and frameworks. For example:
 Java: If you prefer a robust, cross-platform language.

13. Continued:
 Phase 1: Planning and Requirements Gathering
 Duration: 2-4 weeks
 Project Kickoff
 Conduct a project kickoff meeting.
 Define project goals, objectives, and scope.
 Requirements Gathering
 Meet with stakeholders to gather detailed system requirements.
 Create a requirements specification document.
 System Design
 Design the overall architecture of the PMS.
 Plan the database schema and user interfaces.
 Risk Assessment
 Identify potential risks and create a risk management plan.

14. Continued
 Phase 2: Development
 Duration: 1-2 weeks
 Database Development
 Implement the database schema.
 Set up data validation and constraints.
 Phase 3: Testing and Quality Assurance
 Duration: 6-8 weeks
 Unit Testing
 Test individual components and functions.
 Integration Testing
 Test the system as a whole to ensure different components work together.
 User Acceptance Testing (UAT)
 Involve end-users to test the system's usability and functionality.

15. Modeling
 Models in software engineering is created to understand software
requirements, and the designs that will help to achieve those
requirements.
 During system requirement and design activity, system must be modeled
as components and relationships between these components.
 Modeling gives detail system specification in the form of graphical
representation.
 Example of such modeling tool is system flowchart

17. System flowchart

18. Construction
 This activity combines code generation (either manual or automated) and
the testing that is required to uncover errors in the code.
 During the construction phase of a Pharmacy Management System (PMS)
in software engineering, code generation is a critical part of transforming
the system design into a functional software application. Below are the
steps involved in code generation during this phase:

19. Continued
 1. Implementation of Core Functionalities:
 1.1. Database Implementation:
 Develop code to create the database tables and relationships based on the
database schema designed in the previous phases.
 Write SQL scripts or use an Object-Relational Mapping (ORM) framework
to interact with the database.
 1.2. User Authentication and Authorization:
 Implement code for user registration, login, and password management.
 Develop code for role-based access control (RBAC) to enforce security
policies.

20. Continued
 1.3. Inventory Management:
 Code features for adding, updating, and deleting products in the
inventory.
 Implement product tracking, including quantity, price, and expiration date
management.
 Develop barcode scanning functionality if required.
 1.4. Prescription Management:
 Code functionality for recording and processing prescription details.
 Implement prescription verification checks based on established rules.

21. Deployment
 The software (as a complete entity or as a partially completed increment) is
delivered to the customer who evaluates the delivered product and
provides feedback based on the evaluation.
 The deployment phase in software engineering is a critical step in the
development process where the software is made available for use by end-
users or clients.
 Deploying a Pharmacy Management System (PMS) involves several
important steps and considerations:
 Planning for Deployment:
 Define deployment goals and objectives, such as the number of users,
hardware and software requirements, and expected performance levels.

22. Continued
 Infrastructure Setup:
 Ensure that the necessary hardware and software infrastructure is in place. This
includes servers, databases, network configurations, and any third-party
services or APIs the system relies on.
 Testing:
 Before deploying the system to production, thoroughly test it in a staging or
testing environment. This should include functional testing, security testing,
and performance testing to identify and fix any issues.

23. Continued
 Monitoring and Support:
 Implement monitoring tools to keep an eye on system performance and detect
issues in real-time. Set up a support team or process to address any user
inquiries or technical problems.
 Backup and Disaster Recovery:
 Implement robust backup and disaster recovery plans to ensure that data can
be restored in case of hardware failure, data corruption, or other unforeseen
events.
 User Acceptance Testing (UAT):
 Before the final deployment, conduct UAT with real users to gather
feedback and ensure that the system meets their needs.

24. Continued
 Post-Deployment Evaluation:
 Continuously evaluate the system's performance and gather feedback from
users. Make improvements and updates as necessary to enhance the
system's functionality and efficiency.
 Deployment of a Pharmacy Management System is a complex process that
requires careful planning and execution to ensure the system's reliability,
security, and usability in a critical healthcare setting. It's essential to involve
all stakeholders, including pharmacists, IT teams, and compliance experts,
in the deployment process to ensure a successful outcome.