Comsats University Abbottabad

Department of Computer Science

Software Requirement Engineering
Assignment 3
Name: Anees Ahmed.
Registration No: SP20-BSE-053.

Question # 1:
Analyse the stakeholder groups below and list down elicitation techniques you
would use to elicit system requirements?
Passengers in the baggage handling system
Cashiers in the Grocery mart
Doctors in the IoT healthcare system
Answer:

Passengers in the baggage handling system:

• Domain Analysis
• Questionnarie
• Observation

Cashiers in the Grocery mart:

• Focus Group
• Prototyping
• Interviews

Doctors in the IOT healthcare system:

• Survey
 • Interviews
• Brainstorming

Question # 2:
Demonstrate how Inspection is better technique for removal of defects in
requirement engineering?
Answer:

Why Inspections?

Inspections enable us to remove defects early in the software life cycle, and it is
always cheaper to remove defects earlier than later in the software life cycle. It's
important to note that Inspections are a way to remove defects at a lower cost, not a
way to prevent defects from occurring.
The combination of design and code inspections usually removes at least 70% of
the defects in a product, Detection of design defects costs 6 times more using
testing than by using inspections, Code inspection at NASA's Software
Engineering Laboratory found 20 to 60 percent more errors than testing did.
Why should you inspect software?
• Code Inspection Pays For Itself
• Code Inspection Powers Up Testing Strategies
• Code Inspection Boosts Productivity
• Code Inspection Makes Testing Cheaper
• Code Inspection Increases Agility

Question # 3:
Examine whether requirements account for future scalability and enhancements?
Answer:
“Recognizing the scalability requirements of an application are very
important.It isimportant to understand what the projected future usage, user
growth, and data growthwill be in the future.A good rule of thumb is to then
multiply this by a factor of 2 or 3and develop the system based on that projected
future growth.It is important that yourdevelopment environment be continually
tested against this high usage and ensure thatyour development methods, strategy,
tools, environment, and connected systems willeffectively scale as well.”

“Also, regardless of the future requirements to scale, experience will

demonstrate thetype of development or tools to use that will scale well that do not
necessarily have animpact on the development time or effort required.These are
approaches that shouldalways be used, and they are a testament to the skill and
experience of the developer orthe individual leading the developers, such as the
Software Architect.An example ofthis would be in developing your database views
or queries:It is known, based onexperience that there are good ways to develop
these queries that will give the bestperformance out of the box versus other designs
that may give the same results, but areslower, inefficient, and don’t scale well.”“By
overlooking the importance of scalability, there is the potential for complete
systembreakdown when the usage of the system exceeds its capacity.This will
leavedevelopers scrambling to spend additional time to fix the core scaling
problems of thesystem or force a potentially expensive purchase of beefier
hardware (that otherwiseshould not be required) to support a badly scaling
system.”

Question # 4:

Analyse the examples given below and create a list of Functional non-functional
requirements (at least 3 each).
Webstore (e.g., Daraz.pk)
Game (e.g., Cards game)

Answer:
For Webstore:

Functional Requirement:

1. Live Chat
2. shipping and payment system integration.
3. Mobile friendliness.
4. social networking
5. integration with third parties.
Non-functional Requirement:
• Usability.
• Reliability.
• Security.
• Scalability.
• Maintainability.
• Performance.
• Availability.
• Portability.
• Efficiency.
• Testability.
• Flexibility.
• Reusability.
• Interoperability.
For Game:

Functional Requirement:

1. Gamepay Character.
2. user Interface.
3. Rewarding System.
4. Media Content.

Menu Items REquirements:

1. view profile.
2. Help.
3. settings.
4. Missions.
 5. Shop.
6. Inventory.
7. Mail.
8. Friendlist

Non-Functional Requirement:
• Usability.
• Reliability.
• Security.
• Scalability.
• Maintainability.
• Performance.
• Availability.
• Portability.
• Efficiency.
• Testability.
• Flexibility.
• Reusability.
• Interoperability.

Question # 4:
Suppose you are going to make an application similar to Skype.
List down Scope for your app.
Construct a use case diagram for the user of the app.
Create level 0 and level 1 DFD for the app.
Develop an activity diagram for user making a video call/voice call to his friend
Answer:
• Scope:
Project Scope Skype was founded in 2003 by Niklas Zennström, from Sweden, and
Janus Friis, from Denmark. The Skype software was created by Estonians Ahti
Heinla, Priit Kasesalu, and Jaan Tallinn. The first public beta version was released
on 29 August 2003. Skype offers a number of features based around calling (both
free and paid), messaging (including instant, voice and text messaging (SMS)),
video chat, and file and screen sharing.
• Overall Description:
• Product Perspective
Skype is essentially a freemium voice-over-IP service, that allows registered users
to communicate online via online video calling, instant messaging, and mobile
chat. Though relatively young in the grand scheme of things, the software
application is arguably the best method for users to communicate long distance,
whether they are looking to conduct multi-party business meetings or merely send
short, video messages between friends and family. The software requires no more
than an internal or external camera and microphone, often built-in your computer
or smartphone, and an active Internet connection. Calls and messages within Skype
are free, but those to landline and mobile phones will cost varying amounts
depending on the region and accompanying subscription plan. Although some cost
more than others, paying for the premium services is typically far cheaper than
purchasing a dedicated phone or texting plan on your own
• Mobile Apps:
In 2012, the website launched Mobile App for Smartphone users. The skype app
was designed for Blackberry, Android, windows and iPhone devices. With the
launch of mobile Apps and HTML site, more than half of traffic inflow happened
through Apps and Mobile sites.
• Calling
• Skype to skype call
• Calls to mobile and landline
• Group calls
• Skype numbers
• Video:
• One to one
• Group chat
• Message
• Emojis and emoticons
• Internet messaging
• Send texts
• Voice message Sharing
• Send files
• Screen share
• Group screen
 • Send contacts
• Hardware interface
• 128 MB of RAM required
• Processor
• Internet
• Mouse
• Keyboard
• Camera
• Microphone
• Product Features
The Skype application should work 24 hours. The application identifies a customer
by a user Id and a password. It collects information about the user. It then
communicates the information provided by the user to the concerned organizations.
Now they user can start using the functions of skype by selecting the function such
as video call, chatting, messaging etc. the system must handle concurrent
applications running with multiple users. The system should be secure from
external people.
• User Classes and Characteristics
Characteristics:
There are several users of the Skype:
• Users are simply members which use application of different purpose.
• Maintainers must be experienced network administrators.
• Design and Implementation Constraints
• Login
Validate user
• Validate user.
• Valid username and password
Validate for Wrong user name and password:
• Validate for wrong password.
• If username not correct, prompt error message, "wrong username"
• If password is wrong , prompt error message, "wrong password"
Users
• Business conferences
 • Meeting
• Intercultural exchange
• Marketing
• To connect people socially
• Social media
• Assumptions and Dependencies
• Hardware never fails
• Bad internet connection
• User unavailable(offline)

Part B:
Draw 0 level and 1 level DFD:
0 Level DFD:

First Level DFD:

Activity Diagram:

Usecase Diagram: