SWEN User Acceptance Testing

Today our team learnt how to perform a higher level of testing - User Acceptance Testing (UAT). It is recommended that this testing be done at least twice: one for the user to familiarize with the program and the other to suggest improvements on it. :P

The three different types of UAT are:
Black Box Testing - examine the input and output for errors.
White Box Testing - examine the coding placing for errors.
Regression Testing - examine if a newly added function affects old functions and causes error.

The MAIN difference between UAT and Debugging are:
UAT - looking for errors.
Debugging - fixing program errors found.

Interview With Jacob

Today we had interview with Jacob, end user working at a department of Sonium. He had working experience of couple of years. He currently using Microsoft Outlook and is very supportive of MS Outlook and he like most of the featurs of Outlook.

He faced problems managing the appointments as his colleague work using papers, many papers (no sticky-note). Therefore, he want the PIMS to be able to record the appointments and most importantly, search appointments.

To-do list to be able to share with people more efficiently.

Contact list to be able to compose email upon clicking on contact.

We will be working on the software requirement report base on the interview with Peter and Jacob. The report will contain the fucntional requirements and also user interface design.

We highly suspect Peter and Jacob are twins. But Jacob deny and had hatred towards Peter. We hope they'll resolve their relationship one day. Jacob is very cunning. VERY CUNNING.

TGIF :D

Learning Template - SURPRISE!

What we know	What we don’t know	What we need to find out	Who is finding out & How to go about finding?
Interview Peter to gather information needed	What information to gather	What information to gather	INTERV IEW PETER & ONLINE RESOURCES.
Interview end user to gather information needed	What are the software requirement for the PIMS	What are the software requirement for the PIMS
Prepare the requirement document to list the PIMS features.	How to get the specific information from the users.	What are the functions for each of the features in the PIMS. Eg. How many users will be using the system.
10 minutes presentation.	What are the functions for each of the features in the PIMS. Eg. How many users will be using the system.	The characteristics of the user, system, role.
Requirements are WHAT the system will do, NOT how the system will perform	The characteristics of the user, system, role.	What is the system boundaries.
The stakeholders.	What is the system boundaries.	What are the non-functional constraints of PIMS. E.g. User friendliness, performance
	What are the non-functional constraints of PIMS. E.g. User friendliness, performance
	Capturing correct and concisely  requirement.

Day 10, Meeting 7

We presented to Mr Chong our project plan and software process (Throwaway Prototype) adopted.

Day 5, Meeting 4

URGENT CALL-BACK MEETING

Current listening music : ella ella eh eh eh eh eh

You can stand under my umbrella ella ella eh eh eh eh eh~

It's raining heavily.. our mood is drench, our clothes is wet.. underwear also wet

Today is sunday, we're call back to sch for urgent meeting.

PPT slide is done up for coming friday presentation, script is still incomplete.

Day 3, Meeting 3

Today Lokman was late.

It's friday and he need to go to the mosque to pray.

He pray and pray, we wait and wait..

Finally he came! We share with him our mentos sweet and it taste like medicine.

We went to source out books from the library and borrowed 3 very useful, resourceful, powerful, good, intellectual book from TP library.

We made discussion regarding the benefits and advantages of our chosen SW processess (top secret).

We also manage to come up with a project plan.

BYE. TGIF. CYA, SOON.

Day 2, Meeting 2

Day 2, we research on the different types of software processes.

We manage to find the appropriate SW process for the PIMS.

Details will be mail to you.

Brought to you closely by SWENSEN ICECREAM. :)

Learning Template Lab1

Hi Mr.Nalaka,

We are group one of SWEN. Our pratical group is P03. The team consist of Lokman, Phyo, Kaiwen and Ryan. The Lab 01 learning template is below.

What we know	What we don’t know	What we need to find out	Who is finding out & How to go about finding?
Develop a personal information management system	What is project plan?	What is project plan?	Group Ways to find : Books & Internet
Project has not been even half completed	What is software process?	What is software process?	Group Ways to find : Books & Internet
Need to propose a SINGLE software process	What is waterfall approach?	What is waterfall approach?	Phyo, Lokman Ways to find : Books & Internet
Mr. Chong is unhappy	What are the features needed for PIMS?	What are the features needed for PIMS?	Ryan Ways to find : Books & Internet
Two and a half months gone by and nothing to show	Mr. Chong’s requests for the PIMS?	Mr. Chong’s requests for the PIMS?	Kaiwen Ways to find : OLE
Daniel, the previous PM, quit.	The progress of the project.	The progress of the project.	Ryan Ways to find : Books & Internet
Most of the features he wanted were not there	Benefits of any software process.	Benefits of any software process	Lokman Ways to find : Books & Internet
He is unaware of the progress	How to meet the customer’s need?	How to meet the customer’s need?	Kaiwen Ways to find : OLE
2 week deadline		Time management of our project	Phyo Ways to find : Books & Internet
Deliverable Facts
Task 2
Project plan
15 minutes power point presentation
Software process adopted
Explain the project plan
Benefits
How it meets customer needs