Sri Ramakrishna Engineering College: Autonomous Examination - NOV 2019 B.E Computer Science and Engineering
Sri Ramakrishna Engineering College: Autonomous Examination - NOV 2019 B.E Computer Science and Engineering
PART B (5 x 2 = 10 Marks)
Compulsory Question:
16. Complete Requirement Engineering(RE) process for the application: (15 Marks)
(Diagram: 2 Marks)
(Definition: 2 Marks)
(Application Explanation:11 Marks)
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.
Identify functionalities
Indentify main components
Components and interaction
APIs
Environment functionalities: