SRI RAMAKRISHNA ENGINEERING COLLEGE

[Educational Service : SNR Sons Charitable Trust]

[Autonomous Institution, Accredited by NAAC with ‘A’ Grade]
[Approved by AICTE and Permanently Affiliated to Anna University, Chennai]
[ISO 9001:2015 Certified and all eligible programmes Accredited by NBA]
VATTAMALAIPALAYAM, N.G.G.O. COLONY POST, COIMBATORE – 641 022.
Autonomous Examination – NOV 2019
B.E Computer Science and Engineering
16CS215 – SOFTWARE ENGINEERING PRACTICES (ANSWER KEY)
Regulation 2016

PART A (10 X 1 =10 Marks)

1. b) requirements analysis and specification

2. b) Iterative model
3. d) Why are you getting delayed?
4. a) ambiguities
5. c) High cohension, low coupling
6. b) data structures and algorithms
7. d) operational and strategic
8. c) budget
9. b) Strategic risk
10. b) Proactive

PART B (5 x 2 = 10 Marks)

11. process to be iterative and incremental:

 Iterative and Incremental development is a software development process developed in
response to the weaknesses of the more traditional waterfall model.
 Iterative and incremental development (IID) is a process that grows a system feature
by feature during self-contained cycles of analysis, design, and development and
testing that end in the production of a stable, fully integrated and tested, partially
complete system that incorporates all of the features of all previous iterations.
 Scrum and agile are both incremental and iterative. They are iterative in that they plan
for the work of one iteration to be improved upon in subsequent iterations. They are
incremental because completed work is delivered throughout the project.
 SCRUM - At the end of each sprint if approved by the product owner.
 KANBAN - Continuous delivery or at the team's discretion.
 XP (Extreme Programming) - At the end of iteration.

12. IEEE protocol standard for connecting IoT devices:

integrity = ∑[1 - (threat x (1- security))]
= (1 – (0.20 x (1-0.25)))
= (1- (0.20 x 0.75))
= (1- 0.15)
= 0.85
 13. Data Dictionary and its components:
(Definition: 2 Marks &Requirement of Library management System - 1 Marks)
 A data dictionary is a file or a set of files that contains a database's metadata.
 The data dictionary contains records about other objects in the database, such as data
ownership, data relationships to other objects, and other data.
 The data dictionary is a crucial component of any relational database.
Components:
 Domains
 Files
 Fields
 Work fields

14. Importance of design concepts and the basic principles:

Abstraction:
Abstraction is the process or result of generalization by reducing the information
content of a concept or an observable phenomenon, typically in order to retain only
information which is relevant for a particular purpose.
Functional Independence:
Functional independence is a key to good design, and design is the key to software quality.
Refactoring:
Refactoring is a disciplined way to restructure code when small changes are made to the code
to improve its design. An important aspect of a refactoring is that it improves the design while
not changing the behavior of the design; a refactoring neither adds nor removes functionality

15. Contribute to an effective project scheduling:

The factors which influenced planning and scheduling success were: Commitment to
Planning, Human factor (planning, organizing, coordination and motivating skills),
Motivation, Tendering Method, Feedback Capabilities and Project Related Factors.

PART C (5 x16 =80 Marks)

Compulsory Question:

16. Complete Requirement Engineering(RE) process for the application: (15 Marks)
(Diagram: 2 Marks)
(Definition: 2 Marks)
(Application Explanation:11 Marks)

 Requirements engineering (RE) refers to the process of defining, documenting, and

maintaining requirements in the engineering design process. Requirement engineering provides
the appropriate mechanism to understand what the customer desires, analyzing the need, and
assessing feasibility, negotiating a reasonable solution, specifying the solution clearly,
validating the specifications and managing the requirements as they are transformed into a
working system. Thus, requirement engineering is the disciplined application of proven
principles, methods, tools, and notation to describe a proposed system's intended behavior and
its associated constraints.
Process of Requirement Engineering:

Answer any FOUR Questions:

17. Rules for brainstorming process and identify the stakeholders: (15 Marks)
(Rules: 2 Marks)
(Stakeholders Explanation for Event Management: 13 Marks)
Rules for brainstorming process: (keywords)
Brainstorm the right questions
Individual brainstorming
Group Brainstorming
Don’t Forget to Take Action
Build on the Ideas of others
Defer judgment
Stay focused on topic
Fail early and often
Be visual
One conservation at a time
Think user-centric
Go for quality
Go for wild ideas

18. i) Limitation of the traditional process models and 12 principles of Agile: (8 Marks)
(Agile principles: 4 Marks)
(Facts of extreme programming: 2 Marks)
(Limitation of traditional process model: 2 Marks)
12 principles of Agile:
 Satisfy the customer through early and continuous delivery
 Welcome changing requirements, even late in development
 Deliver working software frequently
 Business people and developers work together daily
  Convey information via face-to-face conversation
 Working software is the primary measure of progress
 Maintain a constant pace indefinitely
 Give continuous attention to technical excellence
 Simplify: maximize the amount of work not done
 Teams self-organize
 Teams retrospect and tune their behaviors
12 facts of extreme programming:
 It has proven and established its success on global front
 It is independent of the project size, industry size or industry type.
 The topmost priority of Extreme programming is customer.
 It focuses on delivering what is actually required by the organization rather than talking
about a delivery of big elephant with no clear vision of delivery date.
 Instead of committing to produce everything it promises to produce what is the first need
of organization. So once this gets delivered the next most important requirement becomes
the first.
 This way Extreme Programming never takes complete customer requirements in one go.
It starts with outer periphery moving inwards.
Limitation of traditional process model:
 High costs and wasted budgets
 Unproductive?
 Changes difficult and costly
 Management Bottlenecks
 Lack of transparency

ii) Best practices in software development process & sprint in scrum: (7 Marks)
(List: 2 Marks)
(Explanation: 5 Marks)

 Code simplicity
 Testing
 Code coherence
 Code reviews
 Estimation
Sprint in scrum:
The product owner, scrum master, and the full development team all need to be in
attendance. At Atlassian, we recommend a minimum of one hour for each week of the sprint that
you plan to over in the meeting. For example, start with a two-hour sprint planning meeting to
cover a two-week sprint.
19. Rules for user interface design and user experience model: (15 Marks)
(List: 2 Marks)
(Explanation of UX Model for purchase of book online: 13 Marks)
 UX is not (only) - UI User Interface is a part of User Experience
 Know your audience - User research is a natural first step in the design process
 You are not the user - Testing with real users is an essential part of the design process
 Adapt design for short attention spans - Don’t overwhelm users with too much information
 The UX process isn’t set in stone - Adapt your design process for the product you design
  Prototype before you build a real product - The design phase for digital products should
include a prototyping stage.
 Use real content when designing - Avoid Lorem Ipsum and dummy placeholders
 Keep things simple and consistent - The hallmark of a great user interface is simplicity and
consistency
 Recognition over recall - Showing users elements they can recognize improves usability
versus needing to recall items from scratch
 Make design usable and accessible

20. Steps involved in transform mapping for online examination system: (15 Marks)
(Steps: 2 Marks)
(Explanation for online examination system: 13 Marks)
 Review the fundamental system model.
 Review and refine data flow diagrams for the software.
 Determine whether the DFD has transform or transaction flow characteristics
 Isolate the transform center by specifying incoming and outgoing flow boundaries.
 Perform "first-level factoring." Program structure represents a top-down distribution of
control.
 Perform "second-level factoring." Second-level factoring is accomplished by mapping
individual. transforms (bubbles) of a DFD into appropriate modules within the architecture.
 Refine the first-iteration architecture using design heuristics for improved software quality.

21. i) Quality attributes and process : (8 Marks)

(List of attributes: 2 Marks)
(Explanation: 6 Marks)
Software Quality Attributes are:
Correctness, Reliability, Adequacy, Learnability, Robustness, Maintainability,
Readability, Extensibility, Testability, Efficiency and Portability.
Reason:
Quality attributes become much more important in today's component-based systems. A
well-formed and easy-to-understand documentation on these quality attributes is
necessary in component-based development.

ii) Roles and responsibilities of SQA group: (7 Marks)

(List: 2 Marks)
(Explanation: 5 Marks)
Test engineers/QA testers/QC testers are responsible for:
 Develop test cases and prioritize testing activities.
 Execute all the test case and report defects, define severity and priority for each
defect.
 Carry out regression testing every time when changes are made to the code to fix
defects.

22. i) issues in testing conventional application and testing web application:

(Conventional application: 4 Marks)
(Web application: 4 Marks)
Conventional application:
 It is nothing but validation i.e. testing done while executing the code.
  It is a sort of testing in which the test engineers will check the developed application or
its related parts are working according to the requirements or not.
 The developed components of the application are checked by the tester for whether they
are working according to the expectations of the consumers or not.
 It is focused more up on the functionality of the software system or application.
Web application:
  It is Verification, which involves verification of docs, code etc.
  It is a sort of testing in which Quality Assurance people will check each and every role in
the organization from the Initial Phase of SDLC to the end.
 It starts from the coding phase of the systems development life cycle.
 It keeps a track of the whole software development process on the basis of the quality
assurance principles i.e. whether or not the software has been developed according to the
guidelines and specifications provided by the client company.

ii) Mobile application for creating a help desk: (7 Marks)

Architecture definition: (Diagram: 2 Marks ) (Explanation: 14 Marks)

 Identify functionalities
 Indentify main components
 Components and interaction
 APIs

Environment functionalities: