Week 9 | Design and Prototyping

What is Prototype?
Prototyping is the process of building a model of a system. It was the first example that you do similar to the product but it is used for testing before the real one being publish. In terms of an information system, prototypes are employed to help system designers build an information system that intuitive and easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis phase of the systems development life cycle. It can be in many ways but usually it was a paper-based outline of a screen or a set of screen, 3D paper or cardboards mock-up, stacks of hyperlink screenshot or electronic picture.

There two types of prototype:
- Low fidelity prototype is a prototype that is sketchy and incomplete, that has some characteristics of the target product but is otherwise simple, usually in order to quickly produce the prototype and test broad concepts. For example, storyboard, sketching and prototyping with index cards.

- High fidelity prototype is a prototype that is quite close to the final product, with lots of detail and functionality. From a user testing point of view, a high-fidelity prototype is close enough to a final product to be able to examine usability questions in detail and make strong conclusions about how behavior will relate to use of the final product. For example, prototype of a software system developed in Visual Basic.

Advantages of Prototyping :
-Developers receive quantifiable user feedback.

-Reduces development time.
-Results in higher user satisfaction.

-Reduces development costs.
-Requires user involvement.

Disadvantages of Prototyping :
-Sometimes leads to incomplete documentation.

-Developers can become too attached to their prototypes

-Can lead to insufficient analysis.

-Users expect the performance of the ultimate system to be the same as the prototype.
-Can cause systems to be left unfinished and/or implemented before they are ready.

Prototype model vs real model

AZANISA 

1102702292

Week 8 | Functional Requirements

Functional requirements

Some of the things need requirements as well as we in some cases. I will talk about the Functional Requirement. In order to achieve functional requirement, we need to follow above steps.


Goal > Use case > Functional Requirement > Design > Implementation


Data Gathering
-We should do data gathering to get the best result!
-These are the steps for data gathering :

• Classroom Assessment Techniques
• Document analysis
• Experiment
• Focus group
• Interview
• Observation
• Portfolio
• Product analysis
• Survey
• Usability

Muhammad Syafiq Bin Ridzuan
1102701969

Week 8 | Non-functional Requirements

Non-functional Requirements


Non-functional Requirements have also been called the 'ilities' because they are most simply expressed like this:

•  usability
• reliability
• interoperability
• scalability
• security

A simple way to define non functional requirements is to match answer with question and define as non functional any requirement with no direct impact on individual user experience.

Non functional requirements have no direct impact on individual user experience (R. Doisneau)

There are other ones:

• Time to market
• Cost
• Speed
• [RAM]
• [secondary storage]

Anis Afiqah Mohd Farid
1102701839

Week 8 | Requirement

A requirement is an objective that must be met. Planners cast most requirements in functional terms, leaving design and implementation details to the developers. They may specify price, performance, and reliability objectives in fine detail, along with some aspects of the user interface. Sometimes, they describe their objectives more precisely than realistically.There is two types of requirement where functional and non-functional. 

Functional specifications 

describe the necessary functions at the level of units and components; these specifications are typically used to build the system exclusive of the user interface.

Non functional

Functional specifications describe the necessary functions at the level of units and components; these specifications are typically used to build the system exclusive of the user interface.

ABDUL HADI BIN ABDUL HARIS

1102702580

Week 8 | Identifying Needs and Establishing Requirement

What is requirements?
It is specifies what it should do or how it should perform. It should be specific, unambiguous and clear as possible and we must know how to tell when they have been fulfilled.

Establishing Requirement

What do users want and need? Requirements need clarification, refinement, completion, re-scoping. Input which is requirements document and output which is stable requirements. Why establish? Requirements arise from understanding users needs and it can be justified & related to data.

Two types of requirements
- Functional
- Non-functional

Characteristic of Requirements
- Physical Environment
- Social Environment
- Organizational Environment
- Technical Environment

User Characteristics
- When you createa application, you must know who are the user
- User’s abilities and skills, user’s nationality, user’s education background and etc.
- Any one product may have a number of different user profiles

Usability Goals => Effectiveness, Efficiency, Safety, Utility => How well the users can perform

User Experience Goals => Fun, Enjoyable, Pleasurable, Aesthetically, Pleasing => The perception of the users

In the nutshell,
- Scenarios  can be used to articulate existing and envisioned work practices.
- Use cases can emphasis on user-system interaction. Its from the user’s perspective, not the system’s.
- Task analysis techniques such as HTA help to investigate existing systems and practices
- Essential use cases

- Getting requirements right is crucial

- There are different kinds of requirement, each is significant for interaction design

AZANISA

1102702292

WEEK 8 | IDENTIFYING NEEDS AND ESTABLISHING REQUIREMENTS

According to wikipedia, a requirements means a singular documented physical and functional need that a particular product or service must be or perform. There is two types of requirement where functional and non-functional. Functional requirement means that it shows what the system should do. For example, word processor. When we want to write an article, it must say that we should support a variety of formatting style. Non-functional requirement means it will run on a variety of platform and functioning on 64M of RAM. 

IN interaction design, there is several requirement such as functional requirement, date requirement, environmental requirement, user characteristic, and usability goal and user experience goals. 

Functional requirement

• what the product should do

Date requirement 

• state the size, accuracy, value, and other information of the required data. 

Environmental requirement

• circumstances in which interactive product will be operated.

User characteristic 

• user characteristics is to see users ability and skills, nationality, preferences, educational background, physical or mental disabilities. 

Usability goals and user experience goals

• Usability goals - safety, effectiveness, efficiency, utility
• User experience - fun, enjoyable, excitement, pleasing

AISYAH ALWANI

1102702359

Week 7

There's no post on week 7 due to the assignment briefing in class :)

Thank you!