SE 3 & UXD

30.PridE and IPM+ have been discussed in the following slides.
PCB: PCB ( Process Capability Baseline) gives the actual performance of projects. In essence, it is the capability of the Organization. It collates performance data from various projects across the organization. PCB can be accessed from Quality home page.
PCB is stratified by
Project type (Dev, Maintenance, Re Engineering etc),
Language Level: High Level, Low level
Size of project: Large projects, Small projects etc
Based on data of past projects, Process Capability baseline specifies
 performance of the process
 what a project can expect when following the process.
Process baseline defines the productivity, quality, effort, defect, etc.
Using the capability baseline, a project can predict, at a gross level,
the effort needed for various stages,
the defect densities likely to be observed during various defect detection activities and
quality and productivity for the project

PDB: PDB (Process DataBase) is used for collecting metrics at closure of a project. It contains closure report information. It can be used a source for providing inputs for estimation of projects based on past/history data. This application is accessible to all Infoscions. Data entry and authorization of the closure report information is available only to a limited few which typically are being done by the SQAs. All others have access to only the reports.
The closure reports give
General information on the project (contact personnel),
Estimates of effort and Schedule,
Rework effort across the different Life cycle stages
the breakup of defects detected at different stages
information of when defects were injected,
the top three Risks involved in the project.

Process Assets: At the unit level, Templates, checklists required are the process assets.

Probe Dash Board: Probe Reports the health of the project within line of control using defect deviation, schedule deviation and effort deviation information from milestones along with factors like risks to determine the health of projects.

Tools Group vision and activities have been discussed in this PPT.

ENCORE: ENCORE (ENterprise Consortium for REuse) is discussed in this PPT.

31.Maintenance can therefore be categorized in to three categories;
Major Enhancements:Applying a major change to the system,Requires Requirement elicitation and Design
Bug Fixes.Production Support:Addressing system failure and customer complaints,Requires deeper system analysis to understand the problem and fix it
Minor Enhancements: Small changes at module level,Impact analysis is an important activity,Requirement elicitation and Design may be required but on a small scale

32.Infosys Project Management Process consists of 3 stages
Initiation:Starts when contract/project authorization is available
 Major activities are project planning and associated activities
Execution:Starts as soon as project plan is baselined (finalized)
 Includes project monitoring and tracking
 Re planning
Closure:Starts when customer accepts the work product
 Major activities include collecting feedback, measuring performance

33.Software reuse
Advantages and Benefits of Reuse
 Reduced development effort, time and cost
 Increased productivity and Quality
 Get products to the market faster
Obstacles and Problems of Reuse
 Continued ownership and support
 ‘Not Invented Here’ (NIH) syndrome
 Awareness, difficulties in locating & artefacts’ quality
Reuse at Infosys– ENCORE Team(ENterprise COnsortium for REuse)

34.Types of Asset Reuse:
Black-box Reuse
 Assets are integrated into target system without modification
 Higher benefits, low flexibility
White-box  Reuse
 Assets are modified before integration into target system
  Requires understanding of the inner working of the reused asset
  Requires extensive testing
  Loss of manufacture’s guarantee
 Relatively lower benefit, easier to reuse

35.How do you ensure good Quality consistently?
 Follow Proper Processes
 Carryout Quality Control & Quality Assurance Activities
 Use Defect Prevention Techniques
 Maintain Requirement Traceability
 Use Configuration Management System
 Use Proper Tools
 Capture Metrics, Analyze them and take corrective actions
 Reuse Software Assets

36.Quality Department has a strength of 400+  people
Software Engineering Process Group (SEPG)
Corporate Excellence Group(Strategic Initiatives & Support Functions)
Audits
Process Deployment Group (Process Consultants)

37.Using Data for Improvement
 Understand the importance data
 Use the right set of data
 Collate the right set of data to arrive at current status of projects
 Plan quantitative improvement
 Execute quantitative improvement
 Verify the actual improvement

 (These are possible only if we have metrics and measurements)

38.What do people do in UX design?
Get insights into end user needs
Define end user requirements
Defining and structuring information spaces in software application or web sites
Design navigation paths between information spaces
Design screen elements
Designing the interactivity with information spaces and screen elements
Designing the flow of information and tasks
Choose appropriate representation for information
Design the presentation style and brand. This can visual, auditory and tactile media
Support user needs and goals. E.g. Provide suitable ways of managing and exploring data E.g. Provide ways for collaboration

39.The seven facets of UX:
Useful: As practitioners, we can't be content to paint within the lines drawn by managers. We must have the courage and   creativity to ask whether our products and systems are useful, and to apply our deep knowledge of craft and   medium to define innovative solutions that are more useful.
Usable: Ease of use remains vital, and yet the interface-centered methods and perspectives of human-computer interaction   do not address all dimensions of web design. In short, usability is necessary but not sufficient.
Desirable: Our quest for efficiency must be tempered by an appreciation for the power and value of image, identity, brand,   and other elements of emotional design.
Findable: We must strive to design navigable web sites and locatable objects, so users can find what they need.
Accessible: Just as our buildings have elevators and ramps, our web sites should be accessible to people with disabilities   (more than 10% of the population). Today, it's good business and the ethical thing to do. Eventually, it will   become the law.
Credible: Thanks to the Web Credibility Project, we're beginning to understand the design elements that influence whether   users trust and believe what we tell them.
Valuable: Our sites must deliver value to our sponsors. For non-profits, the user experience must advance the mission.   With for-profits, it must contribute to the bottom line and improve customer satisfaction.
------------
Questions for the seven facets

Useful:  Does the system make a difference to end users? Is it useful?

Usable: Are the features easy to use? The common usability metrics are:
             1. Task success rate: How many people are able to complete a given test task?
             2. Task completion time: How long do people take to complete a task?
             3. Error rate: How many errors do people make while doing the tasks?
             4. Incidence of help: How many times did users ask for assistance to complete the task?
             5. Subjective satisfaction: Overall how satisfied are users with a particular task or system?

Desirable: Does the system look attractive? Communicate a brand?

Findable: Is the system locatable? Are the features in the system findable?

Accessible: Does the system support users with special needs? (reduced vision or physical ability)

Credible: Is the system trustworthy?

Valuable: Does the system deliver value to its sponsors?

40.Key Focus Areas in UX: 1 of 5
User Research
 Discover end user’s real needs.
 Look for insights that can set a direction for design
Recommended SDLC phase
 Requirements phase
Key Focus Areas of UX: 2 of 5
User Interface Design
 Information architecture
 Interface design
 Interaction design
 Rapid prototyping
Recommended SDLC phase
 > 75% in Requirements phase.
 < 25% in HLD phase.
Key Focus Areas of UX: 3 of 5
Visual Design
 Designing the presentation style
 Communicates the brand
Recommended SDLC phase
 Starts in requirements phase
 Closes in high level design phase
Note
 Increasingly designers are supplementing visual design with auditory and tactile interfaces
Key Focus Areas of UX: 4 of 5
User Assistance
 Inline and external help.
 Creating online and print versions.
Recommended SDLC phase
 Starts in the Requirements phase
 Completes after the coded pages are available
Key Focus Areas of UX: 5 of 5
Usability Inspection and Usability Testing
 Validate if end user requirements have been met
 Evaluate and quantify usability
Recommended SDLC phase
 Starts in the requirements phase itself. Early rapid prototypes facilitate validation of user requirements with  stakeholders
 Read speaker notes for more details

41.UX in Infosys
Communication Design Group
 Central department for UX at Infosys
Other units that have creative teams:
 SI (Systems Integration)
 Finacle
 SETLabs
 Internal Communication, HR

42.MYTH!
 Code first, add UX later!
 You don’t need user research!
 UX is only beautification!
 UX cannot be measured!
 More features = better product!
 User testing is project’s last step!
 Rapid prototypes waste time!
 Help messages are not critical!
 UX should look different!
 Good designers can’t go wrong!

43.Wireframes and Prototypes
Wireframes are:
 Intended to roughly portray features
 Characteristics
  Low-fidelity
  Rough ideas
  Minimal or no graphics
  Minimum details
  Uses black and white
  Does not use color
Prototypes are:
 Intended to precisely specify features
 Characteristics:
  High-fidelity
  Detailed mockup
  Graphic specifications
  Interactivity details
  Shows color scheme

44.Case  Study : Identify Reusable assets:
Login
Workflow
E-mail utility
File upload
Report Framework

 

45.When to use wireframes?
 Best used in requirements phase to visualize overall requirements.
When to use prototypes?
 Best used in requirements and HLD phases to sign-off detailed UI requirements.
 But wireframes are also used in other phases to get consensus on scope or requirements changes

 

46.Elements of Engineering Approach
Engineering Approach uses …
 Processes
  Set of activities needed to produce the system
 Methods
  Structured development approach for expected quality outputs adhering budget and time
 Tools
  Provide support for executing processes
Software Engineering uses …
 Processes
  Software Specification
  Software Development
  Software Validation

 Methods
  Structured Methods
  Object Oriented Methods
 Tools
  MS Project
  Coding Tools
  Testing Tools