ICT581 Information Systems Principles and Practice

Assingement1: Weddings Parties Everything system

LAKPA TENZIN
 Table of Content

Sl. No. Content Page No.

1. Trigger & Benefit
2. Stakeholders
3. Assumptions
4. Functional requirements
5. Non-Functional Requirements
6. User Goal technique
7. Event Decomposition technique
8. Domain model class diagram

1 Lakpa Tenzin,34768257
Question 1: 
Describe the trigger of the Weddings Parties Everything system (WPE) and explain the
benefit WPE would bring. Write in your own words and explain the reasons for each. 

With more events happening every day, weeding, parties, catering service system is a quickly
expanding web company that connects clients looking for a caterer for their event with
companies that offer catering. The platform will launch the business by creating system
automation and efficient techniques to expand the business by links together customers who
need a caterer for their event with businesses that provide catering. The caterer and customers
are the two parts of the system.  

These are the following benefits weeding, parties, catering service system (WPE) would
bring in their new system:

1. WPE will be able to refer the finest caterers to a client.

2. The customer reviews will assist other customers in locating legitimate catering tasks.
3. It will continue to be successful in getting catering work booked because of its
reliable company.
4. Professionalism would be increased.
5. It is cost saving and it contributes to company expansion.
6. The quick service improves the website's reciprocal contact.

2 Lakpa Tenzin,34768257
Q2. List the main stakeholders for the Weddings Parties Everything system (WPE). For
each stakeholder, describe their interest in the system and what aspects of it are of
particular relevance to them (You do not need to categorize the stakeholders. Don’t
include the systems development team).

The main stakeholders for the Wedding Parties Everything (WPE) system include:

1. Owners /Managers- The most crucial stakeholders are the owners of the company for
which the system is being developed because their operations rely on it. The owners would
choose the system's function and how much it would be integrated into their daily activities.
The owners would have complete authority over the system. 

2. Investors - The other significant stakeholders would be the individuals who invest their
money in the company, as it is their capital that will be used to develop, design, and deploy
the system, as well as parts support the team that will create it and maintains it over time.

3. Customers - Customers would also be included on the list of WPE system partners since
they would be the system's final consumers and their input on how the system is used would
influence its future functionality.

3 Lakpa Tenzin,34768257
Q3. Make assumptions about where information in the case is incomplete and where WPE can
be improved around a given case. Discuss the proposed assumptions.

1. Facility assumptions
Your project team may make facility assumptions about where the project production can
take place. For example, if your project requires experiments, your team may make
assumptions about available labs. Other facility assumptions may concern office space where
your team can work and organize information.

2. Technology assumption

3. Infrastructure assumption
Infrastructure assumptions refer to what supportive tools might be available for teams to use
throughout the project. For example, your project may assume that you can use certain
communication tools while working on the project. This might also include specific
assumptions about the team's ability to discuss the project in real-time over the company
messaging app.

4. Design assumptions
You may make assumptions about different design tools or practices your team can use while
working on a project. For example, if your project requires visual assets for promotional
materials, you might assume that design tools are important for the project. This assumption
may also be that your team can use existing company design software to meet the project's
needs.

5. Business assumptions
Business assumptions can refer to any business outcomes that are expected because of
specific projects. For example, if you assume a marketing project can drive brand awareness,
you're making business assumptions. Another related assumption might be that promotional
campaigns increase product or service sales.

6. Financial assumptions
Other standard assumptions can be financial. These are usually assumptions made about
project budgets, as they're integral to any project. For example, if you expect to need a set
amount of money and only that, you're making a financial assumption about your project.

7. Standard assumptions
Standard assumptions refer to ideas about the best approach or strategy for your project. For
example, when planning your project, you might reference different strategies and select one.
This process of choosing a strategy is a standard assumption because you're assuming one
way of executing your project is better than another.

4 Lakpa Tenzin,34768257
Q4. (a) List and briefly describe the main functional requirements for the WPE. (b) List and
briefly describe the main non-functional requirements for the WP

What is a functional requirement?

F unctional requirements are the details and ins tructions that dictat e how
s oftw are performs and behaves . Typical ly, softw are engineers create and
apply functional requiremen ts to s oftw are during the development s tages of
a project to ens ure their s oftw are is eas y to us e and operational. Functional
requiremen ts can vary in behaviors , features and protocols , depending on
the us er' s indus try. F or example, a video game des igner may us e different
functional requirements in softw are that focus on game des ign, while a
teacher may us e functional requirements that focus on s tudent us ability.

F unctional requirements examples

H ere are s ome examples of functional requirements for different types of
s oftw are:
Webs ite
F unctional requirements for a w ebs ite explain the features a w ebs ite needs ,
how us ers can acces s w ebpages , w hat happens w hen us ers click on certain
parts of the w ebpage and how the webs ite appears in a brows er. F or
example, perhaps a client from a s ales agency w anted to create an e-
commerce w ebs ite w here cus tomers can learn about their products , submit
inquiries , brow s e inventory and place orders . S ome of the functional
requiremen ts for the w ebs ite might include:
• The background color for the main page is light yellow .
• Each product has an "add to cart" button that places that item in a
virtual shopping cart.
• The checkout s ecurely proces s es credit cards from all major vendors .
• The s oftw are pas s es all s ecurity requiremen ts .
• The w ebs ite allow s company adminis tra tors to acces s order data.
• U s ers can click the s ide navigation page to brow s e different w ebs ite
s ections .

5 Lakpa Tenzin,34768257
• A w eb page contact form s ends emails directly to the s ales manager' s
inbox.
M obile app
F unctional requirements for a mobile app include the s pecific features that
help us ers navigate through the application, acces s links and view the
applica tion from their mobile device. F or example, perhaps a clothing
company w anted to create a mobile app that allow s us ers to order their
clothing through the applicat ion. Here are s ome potential functional
requiremen ts for the app:

• The app allow s us ers to look through catalogs of clothing.

• The app requires us ers to ins ert a pas s w ord to enter their accounts .
• U s ers can enter credit card information at the point of s ale page.
• A templat e appears once us ers enter their credit card information
w here they can fill in their shipping details .
• A s oftw are feature in the app allow s us ers to add products to their
cart automati cal ly by tapping tw ice on the item.
C us tomer management s ys tem
F unctional requirements for a cus tomer management s ys tem allow
companies to interact w ith cus tomers , s tore cus tomer information and share
information w ithin a company' s netw ork. For example, an ins urance agency
might us e a cus tomer managemen t s ys tem where ins urance agents can
interac t w ith clients , update and change policy information and exchange
cus tomer information w ith other ins urance agents at their company. H ere
are s ome functional requirements they might cons ider for the cus tomer
managemen t s ys tem:
• The s ys tem allow s ins urance agents to acces s it us ing a pas sw ord and
their employee identifica tion number.
• Ins urance agents mus t receive management verification before
making a change to cus tomer information.
• The s oftw are archives all deleted policy information.
• The s ys tem tracks and records all cus tomer interactions .
• A s oftw are feature enables the sys tem to perform routine s ecurity
checks to verify the identity of ins urance agents .
S ales softw are

6 Lakpa Tenzin,34768257
F unctional requirements for s ales s oftw are explain the features that help
s ales profes s ionals promote products , acces s client information, perform
trans actions and track previous s ales . F or example, perhaps a makeup
brand wants to us e s ales s oftw are w ith functional requirements that allow
them to facilitat e trans actions , take orders and create product des criptions .
Thes e functional requiremen ts might include:
• A point- of-s ale w ebpage to track all trans actions .
• S ys tem s oftw are requires us ers to enter their financia l information
upon creating an account.
• The background color for all w indows is a vibrant blue.
• The s oftw are pulls information from previous trans actions to
encourage us ers to purchas e more products .
• U s ers can navigate the s oftw are eas ily by us ing navigationa l buttons
that s how where to locate s pecific products .
V ideo game s oftw are
V ideo game s oftw are includes features that allow us ers to defeat levels ,
w in challenges and build up their problem- s olving s kills . F or example, if a
video game company w ants to releas e a game that encourages us ers to
figure out challenges and increas es the amount of difficulty for each level,
the functional requiremen ts may include:
• U s ers can operate a controller that allow s them to control characters
in the game.
• Each level increas es the difficulty of challenges .
• U s ers mus t create a us ername and pas s w ord to play the game.
• The game prompts us ers to verify their identi ty before s tarting each
game.
• The colors of the game change depending on the level.
B enefits of functional requirements
H ere are s everal benefits that us ers and softw are engineers may encounter
w hile us ing functional requiremen ts :
• Identifying functionality of a s ys tem: Functional requirements can
help you identify the features of a s ys tem to s ee w here you may enhance
functional ity.
• S upporting client preferences : If s oftw are engineers create a project
for a client, they may create functional requirements bas ed on the client' s
preferences . For example, if a client reques ts s oftw are that allow s us ers to

7 Lakpa Tenzin,34768257
acces s s everal files at once, then a functional requiremen t may include a
large amount of file s torage.

• Increas ing us ability : Functional requiremen ts increas e the us ability

of the s oftw are. A softw are s ys tem may include a s pecific feature that
makes the s ys tem more convenient for us ers to operate.
What details do functional requirements include?
H ere are s ome details that functional requirements include in softw are:
• Workflow information: D evelopers us e functional requiremen ts to
provide information about workflow management, w hich includes details
about a s ys tem' s performance, applicat ions and interface s etup.
• Legal and us er compliance: F unctional requirements may help
s oftw are engineers meet legal and us er requirements .
• S ys tem changes : F unctional requirements help us ers and s oftw are
engineers identify w ho can make changes to the sys tem, like modifying
data in the s ys tem or changing interface details .
• S ys tem reports : U s ing functional requiremen ts allow s s oftw are
engineers to have detail ed des criptions of s ys tem reports , including how
s oftw are interacts w ith technology and w hat changes are neces s ary to help
a sys tem run more s moothly.
Types of functional requirements
H ere are s everal types of functional requiremen ts :
• C ertific ation requirements : A company may include a functional
requiremen t that requires profes s ionals to have a s pecific certifica tion
before operating a s oftw are s ys tem.
• A dminis trativ e operations : Companies may us e functional
requiremen ts to give specific members of management permis s ion to
handle the softw are.
• R eporting guidelines : Fundamenta l requirements may explain how
us ers can gather and s earch for s pecific data.
• Trans action operations : Thes e examine a s ales trans action, including
the trans action' s entry, deletion, cancellat ion or total charge.
• A udit tracking: Companies may have functional requirements in their
s oftw are that track important data. Us ers may s elect the data they want or
have the s oftw are automatica lly track important data.

8 Lakpa Tenzin,34768257
• External interfaces : When companies include external interfaces in
their functional requirements , they handle interfaces outs ide their main
s ys tem, like a partner' s w ebs ite or a cow orker' s operating s ys tem.
• A rchiving data: F undamental requirements allow companies to
archive outdated data, rather than deleting it, in cas e they need the data in
the future.
• H is torical data handling: F unctional requirements often involve
pulling his torical data from previous trans actions or guidelines to predict
us er preferences .
• Legal requiremen ts : D epending on the indus try, a company may have
s pecific law s and regulations to follow . F undamental requiremen ts ens ure
that a company' s softw are remains compliant.
• A uthentica tion: Functional requirements authenti cate the information
that us ers input into a s ys tem. A sys tem may require pas sw ords to
authorize us ers to acces s information.

9 Lakpa Tenzin,34768257