DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

22PBIC52 – FUNDAMENTALS OF REQUIREMENT ANALYSIS AND

MANAGEMENT LABORATORY
YEAR 2024 – 2025

NAME OF THE STUDENT :

REGISTER NUMBER :
COURSE :
YEAR :
SEMESTER :
 BONAFIDE CERTIFICATE

Reg. No.

This is to certify that the Bona-fide Record of this Practical Work was completed by
Mr./Ms.…………………………………… of B. TECH - IT (CLOUD AND
MOBILE BASED APPLICATION DEVLOPMENT) in the Fundamentals of
Requirement Analysis and Management Laboratory during the academic year of
2024-2025

HEAD OF THE DEPARTMENT STAFF-IN-CHARGE

Submitted for the Practical Examination held on ………………………….

INTERNAL EXAMINER EXTERNAL EXAMINER

S.NO DATE TITLE MARKS SIGNATURE

1. PROBLEM DOMAIN

2. BUSINESS PROCESS

3. ARTIFACTS

4. USECASE SPECIFICATION

5. STORY BOARD

INDEX
 SUPERMARKET MANAGEMENT

PROBLEM DOMAIN

Supermarket management

Requirements:

The supermarket management system must streamline various operational processes, including
inventory management, sales tracking, and customer relationship management. It should enable real-
time inventory updates to prevent stockouts and overstock situations. Additionally, the system must
support efficient checkout processes, minimizing wait times for customers. Integration with various
payment methods, including credit cards and mobile payments, is essential for enhancing the shopping
experience. Reporting features should provide insights into sales trends, customer preferences, and
inventory turnover.

Role Definition: Store Manager:

The store manager plays a crucial role in overseeing daily operations and ensuring the supermarket
runs smoothly. They are responsible for managing staff, including hiring, training, and scheduling, to
maintain an efficient workforce. The store manager must also monitor inventory levels and coordinate
with suppliers to ensure timely restocking of products. Customer service is a top priority, requiring the
manager to address complaints and enhance the overall shopping experience. Additionally, they must
analyse sales data to identify opportunities for improving profitability and customer satisfaction.

Role Definition: IT Administrator:

The IT administrator is responsible for maintaining the technological infrastructure of the supermarket
management system. They ensure that all software and hardware components are functioning correctly
and are updated regularly to avoid disruptions. This role involves troubleshooting technical issues and
providing support to staff on system usage, ensuring minimal downtime. The IT administrator also
implements security measures to protect sensitive customer and transaction data. Lastly, they
collaborate with management to assess new technology solutions that could enhance operational
efficiency and customer engagement.
Here are two Grammarly tools that can help check grammar mistakes in a problem domain:

Grammarly Editor:
The Grammarly Editor is a web-based writing assistant that checks for grammar, punctuation, spelling,
and style errors in real-time as you type. In the problem domain, such as creating project
documentation or technical reports, the editor can be used to proofread the content, ensuring clarity,
correctness, and professionalism. It also offers suggestions for improving sentence structure and word
choice, which is essential when documenting technical processes like artifact management or pipeline
configurations.

Grammarly for Microsoft Word:

Grammarly for Microsoft Word is a plugin that integrates directly into Word, helping users correct
grammar, spelling, and punctuation while writing project-related documents. For instance, if you are
writing use case specifications or step-by-step guidelines for managing artifacts in GitLab CI/CD, this
tool highlights potential errors and offers real-time corrections, ensuring your document is error-free
and easy to understand.
 BUSINESS PROCESS

What is Business Process?

A business process diagram is a visual representation of a process that your company
carries out to achieve goal. It uses standardized symbols to describe each step of the process.

STEPS TO CREATE BUSINESS PROCESS:

 There are seven steps to create a Business Process
 Outline your business process
 Gather necessary information
 Have colleagues offer feedback
 Build your business process with a BPM
 Assign roles
 Set rules and conditions
 Launch and test your business process

Business Process for Supermarket Management:

Creating an efficient supermarket management involves designing a clear and structured process to ensure
accurate and competitive pricing. This process aims to integrate cost data, market insights, and user inputs to
deliver an optimal retail price, keeping in mind taxes, promotions, and profit margins. Below is the structured
business process to ensure seamless functioning

1. Supplier Management: Establish and maintain relationships with suppliers, negotiating

contracts and ensuring timely delivery of products.

2. Inventory Management: Monitor stock levels in real-time, manage reordering processes, and track
product expiration dates to minimize waste.

3. Product Merchandising: Organize and display products effectively in-store, using marketing
strategies to enhance visibility and customer engagement.

4. Sales Transactions: Facilitate efficient checkout processes through POS systems, integrating
various payment methods for customer convenience.

5. Customer Relationship Management: Implement loyalty programs and gather customer feedback
to enhance satisfaction and build long-term relationships.

6. Promotions and Discounts: Develop and manage promotional campaigns, including discounts and
special offers to attract customers and increase sales.

7. Staff Management: Hire, train, and schedule staff effectively, ensuring a well-trained team to assist
customers and maintain store operations.
8. Financial Management: Monitor financial performance through sales tracking, budgeting, and
expense management to ensure profitability.

9. Data Analysis and Reporting: Analyze sales data and inventory reports to identify trends, forecast
demand, and make informed business decisions.

10.Compliance and Safety Management: Ensure adherence to health and safety regulations, as well
as industry standards, to maintain a safe shopping environment.

Supplier Management and Inventory Control:

Effective supplier management is crucial for maintaining a steady flow of products in the supermarket.
Establishing strong relationships with suppliers allows for better negotiation of contracts and ensures
timely delivery of fresh goods. Once products are received, inventory management takes center stage,
involving real-time monitoring of stock levels to prevent stockouts or overstock situations. This
includes tracking expiration dates to minimize waste, enabling the supermarket to offer fresh products
consistently while optimizing inventory turnover.

Customer Engagement and Sales Transactions:

A seamless sales transaction process is essential for enhancing customer satisfaction. Utilizing modern
POS systems allows for efficient checkout experiences, incorporating various payment methods, such
as credit cards and mobile payments. To boost sales, supermarkets often implement customer
relationship management (CRM) strategies, including loyalty programs and targeted promotions.
These initiatives help gather valuable customer feedback, enabling the supermarket to refine offerings
and personalize the shopping experience. By developing strategic promotions and discounts, the
supermarket can attract new customers and incentivize repeat visits.

Staff and Financial Management:

An efficiently managed workforce is vital for smooth supermarket operations. This involves hiring,
training, and scheduling staff to ensure they are well-equipped to assist customers and maintain the
store’s appearance. Financial management plays a significant role in overall business health, requiring
careful monitoring of sales performance and budget adherence to maximize profitability. Regular data
analysis and reporting provide insights into sales trends and inventory patterns, informing strategic
decisions for future growth. Additionally, compliance with health and safety regulations ensures a safe
shopping environment, which is fundamental for customer trust and satisfaction.
Here are two tools used for managing business processes:

1. Bizagi:
*Bizagi* is a Business Process Management (BPM) tool that helps organizations model, automate,
and optimize business processes. It allows users to visually design workflows, define roles, and set up
rules and conditions for each step of the process. For example, in a retail price estimation system,
Bizagi can be used to model the pricing workflow, from data input to final pricing approval, ensuring
that the entire process is streamlined and follows established business rules. The tool also supports
integration with other systems, making it easier to manage complex processes.

2. IBM Business Automation Workflow:

*IBM Business Automation Workflow* combines process and case management to help manage
business processes and enhance decision-making. This tool allows users to automate workflows, track
progress, and collaborate on tasks in real time. In scenarios such as artifact management or retail price
estimation, the tool helps automate repetitive tasks, assign roles to team members, and ensure
adherence to business policies. It also includes analytics to monitor and optimize workflows for better
efficiency.
 ARTIFACTS

The Document that are produced during the requirement management that contains the Supplementary
information for the project team and take Holders.

Software Artifacts:

The document produced during the development process.

 Data model -To proves.

 prototype
 Workflow Diagram.
 Set up script (story board).

Creating attribute for requirement artifact:

For creating attribute requirement in a project, the custom artifact attributes use in custom artifact
type-the predefined and custom artifact

 Tactical entities.
 Integer.
 Date
 Time
 Team member (optional)

Creation of custom artifact datatype:

 Administrator menu.
 Manage project properties.
 Attribute data type tab.
 New Data type.
 Name the description of the datatype.
 kind of the value of the base datatype. (Enumeration values)
 URI/URL
 SAVE
WHAT IS ARTIFACT IN GIT LAB CI/CD?

In Gitlab CI/CD an artifact is a file or directory generated by a job during its execution Artifacti are
used to pass data and files between different stages or jobs within Once a job la completed, its and can
be a CI/CD pipeline. artifacts are saved accessed in Subsequent stages penned in the gitlab UI for
further analysis, deployment or manual Prelection.

PROGRAM:
stages:
- build
- test

build-job:
stage: build
script:
- mkdir output
- echo "Building project..."
- echo "Sample artifact content" > output/build_artifact.txt
artifacts:
paths:
- output/
expire_in: 1 week # Artifacts will be stored for a week

test-job:
stage: test
script:
- echo "Running tests..."
- cat output/build_artifact.txt # Accessing the artifact from the build job
dependencies:
- build-job # This ensures that the test-job can access the artifacts from build-job
Gitlab  Artifacts

STEP 1  Sign in [https://gitlab.com]

STEP 2  click [Gitlab... //Artifact]

STEP 3  Click on the left side bar ["code"] and click "Repository"

STEP 4  Create a new file and give the file name [.gittab-ci.yml]

STEP 5  write the code

STEP 6  Commit the changes [Then the bile gets created]

STEP 7  Click on the left side bar ["build "J and click ["properties"]

STEP 8  get inside the pipeline.

STEP 9  click on the build-job

STEP 10  click on the download in right side

STEP 11  Go to fille explorer and click artifacts and extract.

STEP 12  folder gets created and open output file

(or)
In Step 10 instead of clicking download click browser.
go inside build  output.txt  click the link and the output gets downloaded.
 Here are two tools used for managing artifacts in a CI/CD pipeline:

1. GitLab Artifacts:
GitLab Artifacts are a built-in feature of GitLab CI/CD that allows developers to store,
manage, and pass files (artifacts) between jobs in a pipeline. Artifacts can include build outputs, test
results, logs, or binaries generated during different stages of the CI process. For example, after
compiling code in a build job, the resulting executable can be stored as an artifact and used in a
subsequent deployment job. GitLab also allows users to specify artifact expiration, reducing storage
costs by automatically cleaning up old artifacts.

2. Jenkins Artifacts:
Jenkins Artifacts are files generated by Jenkins jobs during the execution of a CI/CD
pipeline. Artifacts in Jenkins can be any files (e.g., logs, binaries, or reports) produced during a job
run, which are stored and made available for future stages or manual download. Jenkins supports
artifact archiving, making it possible to keep important files for later use or review, even after the job
has finished. Developers can configure the jobs to publish artifacts and also set retention policies for
storage efficiency.
 USE – CASE SPECIFICATION

Use Case Definition: -

A use case describes how a user interacts with a system to achieve a specific goal. For the artifact
management in GitLab CI/CD, the use case would be how a user (such as a developer) uses
GitLab’s CI/CD pipeline to create, manage, and retrieve artifacts.

Steps for Creating Use Case Specification: -

1. Identify Use Case Title:

Clearly define the use case. In this case, it's “Manage Artifacts in GitLab CI/CD.”
2. Define Actors:
Identify the actors involved in the use case. For this scenario, the main actor is the developer,
while the CI/CD system is also an implicit actor (automating processes).
3. State Preconditions:
Document the conditions that must be met before the use case begins. Here, the user must have
access to the GitLab project, and CI/CD must be set up with a .gitlab-ci.yml configuration file.
4. Describe Basic Flow:

Outline the typical steps that occur during the use case. This should include:

a. The process of defining artifacts in the .gitlab-ci.yml file.

b. The steps involved in executing the pipeline.
c. How artifacts are generated and stored.
d. How they are passed between jobs or accessed after execution.

5. Handle Alternate Flows (Optional):

Identify any alternate or exceptional flows. For instance, if an artifact fails to generate or is
missing in subsequent jobs, how should the system or developer handle it?
6. Postconditions:
Define the state of the system after the use case completes. For example, artifacts are available for
download, stored, or passed to the next stage in the pipeline.
7. Special Requirements:
List any specific requirements, such as storage space for artifacts, permissions for accessing
artifacts, or integration with external data stores or systems.
8. Include Non-Functional Requirements (Optional):
Specify any non-functional requirements like performance (e.g., how long the pipeline should take
to run) or security requirements (e.g., artifact encryption or access control).
9. Document with Use Case Diagrams (Optional):
Create a use case diagram to visualize interactions between the actor (developer) and the system
(GitLab CI/CD). This helps illustrate how the developer interacts with the system to manage
artifacts.
 SUPERMARKET MANAGEMENT: -

Actors -

1.Store Manager

2.cashier

3.inventary manager

4. Customer

 Store Manager:

 Monitors sales performance and inventory levels.

 Implements policies and procedures for efficient store functioning.

 Cashier:-

 Process customer transactions at the checkout.

 Handle cash and electronic payments accurately.

 . Inventory Manager :

 Monitors stock levels and manages inventory replenishment.

 Coordinates with suppliers for timely deliveries.

 Customer:

 Customers purchase products to meet their daily needs.

 They offer feedback on products and services,
 USE CASE STORYBOARD

WHAT IS USECASE STORY BOARD?

1. It primarily doesn’t ratant o used in initial stages of the development.

2. It is a reasoning tool to capture the requirements of VI
3. To understand the use ability requirement.
4. It is a high level of understanding of UI
5. The user Interface can be created, Prototype, design, implemented - (Several Versions)

USE-CASE DESCRIPTION:

Boundary class:
1. Static Boundary class - window containment hierarchies.
2. Dynamic Boundary Class - Window navigation path.
3. Capturing the requirement of each Ul.
4. Trace the specific use case drive and approach for software engineering.

Describing the flow of events – Storyboard:

-The following are guidelines on how to describe a flow of event-Storyboard:

1. Start by clarifying the use case itself - not its user interface.
2. Keep action statements brief.
3. Aroid Sequences and modes.
4. Be consistent with the use case.

COMPLETING THE DIAGRAM OF A USECASE STORYBOARD:

Complementing the diagrams of a use-case storyboard" refers to the process of adding additional
context, details, or information to use case diagrams in order to create a more comprehensive
understanding of how a system will work from the user's perspective.
To complement these diagrams, additional elements such as:

 Narrative descriptions or textual scenarios that explain the steps involved in each use case

 Alternative and exception flows that describe how the system behaves in different
circumstances.

 Mock-ups or wireframes that provide a visual guide to the user interface.

 Sequence diagrams or activity diagrams that show the sequence of interactions between
components in more technical detail.

 Screenshots or visual aids for more clarity on how the system might look or behave.

USABILITY REQUIREMENT ON USECASE STORYBOARD:

 Maximum execution time - How long it should take a trained user to execute a Common Scenario of use
case.

 Minimum error rate - how many errors a trained user will average for a use case common scenario of use
case

 Learning rate-It is a measure of time It takes before the user can execute a scenario faster that the
maximum execution time.

Here are two tools used for creating use case storyboards:

1. Storyboard That:

Storyboard That is an intuitive tool designed to create visual storyboards for various scenarios, including
software use cases. It allows users to create step-by-step storyboards, representing how a user interacts with a
system to accomplish specific tasks. For example, in a retail price estimation system, Storyboard That can
visually depict the user journey from entering product information to generating and viewing pricing results.
This helps teams communicate the user experience in a clear, visual format, enhancing understanding across
development and stakeholder teams.
2. Microsoft PowerPoint:

Microsoft PowerPoint is a versatile tool for creating use case storyboards, allowing users to craft slides
that depict sequential steps in a use case. Each slide can represent a different interaction or stage in the use
case, incorporating text, visuals, and annotations to illustrate user actions and system responses. For instance,
a PowerPoint storyboard can depict the flow of data entry, calculation, and price display in an artifact-based
pricing workflow, making it easier for stakeholders to visualize each interaction within the use case.
PowerPoint also supports collaboration and easy sharing for feedback.