Software & system requirement engineering

Requirement Engineering

Assignment <1>

Tool Name <visual Pradigm>

Submission Detail
Date 8,Feburary,2017
Day Wednesday
Submitted to: Miss Sajiya Tariq
Submitted from: Raheela
BT 14034(Morning)
Software & system requirement engineering

Question Number: 1

Requirement analysis is one of the most important phase in Requirements

construction phase .Identify the key practices which are done in

requirement analysis and briefly explains them.

Requirement analysis:

Requirement analysis is also called requirement engineering is the process of

determining the user expectation for a new or modified product. Requirement analysis

involve frequent communication with user to determine feature expectation,

resolution of conflict or ambiguity in requirements as demanded by various user and

documentations of all aspects of project development process from start to finish.

Best practice take composed list of requirements merely as clues and repeatedly ask

“why”untill the actual purpose are discovered. Following are the practices which are

done in requirement analysis.

Stakeholder Identification:

Stakeholder are persons or organization which have a valid interest in the system. They

may be affected by it either directly or indirectly. A major new emphasis in 1990s was a

focus on the identification of stakeholder. It is identified that stakeholders are not

limited to organization employing the analyst. Other stakeholder will include anyone

who operate the system, anyone who benefits from the system or involve the in

purchasing the system.

Software & system requirement engineering

use cases:

A use case is a structure for documenting the functional requirement for a system ,basically it is

a tool for describing the behavior of software .use cases does not describing the internal

working of the system it shows the steps to perform a task so it is very important to create use

cases or workflow diagram to understand how people must interact with a new system so these

helps in describing the user’s need.

Prototyping:

A prototyping is a computer programme that allows user visual application that has not been

yet created. It helps the user and other stakeholder to get an idea of what the system will look.

Prototyping make it easier to take decision .it also proves the communication between users

and developer and we can easily understand the requirement an expectation of users.

Stakeholder interview:

stakeholder interviews are the common technique used in requirement analysis. These

interviews may reveal the requirement that has not identified. However each stakeholder will

have an idea of their expectation or will have visualized the requirement so these interviews

helps in requirement analysis.

Joint Requirements Development session:

Requirements that are unknown to stakeholders and often missed completely or incompletely

defined during stakeholders’ interviews .They can be elicited by conducting JDR session in a

controlled environment where stakeholders participate in discussions to elicit requirements.

Software & system requirement engineering

QUESTION Number: 2

select any RE tool and generate report for this.

Detailed overview of visual paradigm:

visual paradigm is a powerful and cross plate form. It is easy to use design and management tool

for IT system. Visual paradigm features include all the UML diagram and ERD tool essentially in a

system and database design. In addition to modeling support it provides report generation and

code generations. It include the following features

UML modeling:

visual paradigm is UML case tool .we can draw all kinds of UML diagrams including class

diagram, use case diagram, sequence diagram, communication diagram, Activity

diagram,compenent diagram etc….

Database design:

visual paradigm helps in database modeling .we can draw Entity Relationship diagram, ORM

digrams.we cannot model the database table but also stored procedures ,sequences, and

database view in an ERD beside this we can reverse engineering diagram from an existing

database.

Business process modeling:

we can draw the diagrams to aids in the business processing model like data flow diagram,

process map diagram, organization charts ,event drive process chain diagram etc….
Software & system requirement engineering

user story:

user story is a proven technique to capture and maintain user needs. With UeXceler tool we can

write user stories and mange them with use cases and tags. All these can be done with visual

paradigm, a designing environment.

Object relational mapping:

object relational mapping enable us to access relational database in an object relational

approach when coding. Visual paradigm generates object relational mapping layer which

incorporate features such as Transaction support and customizable SQL statements.

Screen short of user work:

Software & system requirement engineering
Software & system requirement engineering
Software & system requirement engineering
Software & system requirement engineering

Pros and corns:

Pros:

Effective IT system

it is effevtive IT sysytem design tool with UML and ERD diagram and it is inovating modeling

tool like Resource Catalog and Transistor make system modeling easy and cost effective.

Don’t Just tell show them

A picture is worth a thousand words .The frame work and storyboard tools provides an

effective way for the end user to preview the system give comments and confirm

requirements

Improve workflow:

Animations are always more interesting than static image that’s why visual paradigm offer a

business process animation features and helps in improving the workflow.

Corns:

increase of vocabulary:

AS Visual Paradigm offer the visual programming language so too much combining of

diagrams could reach a point where abstraction has caused a huge increase in vocabulary.

Concepts are less easy to show:

some concepts are less easy to show in visual programming E.g. for a loop is not easy to

comprehend from a bunch of nodes linking to each other.

Software & system requirement engineering

Visual language generate slow code

Every developer who has faced performance problem knows how hard they are to diagnose

and overcome. Visual language has lack of abstraction often generating slow code.

Recommendations for the tool:

Currently visual paradigm supports generating source code from state and class diagrams only

so it should also create the source code from others diagrams.

Visual paradigm cannot install more than three machines provided that if there is same user

so it should include the feature that it can run on multiple machines with the same user.