1st interview

On last thursday, 23rd August 2007, we had interviewed our clients, which is Pn. Badariah to collect requirements from her.
By following our WBS plan, 1st is to identify the stakeholders then interview the clients. During the interviewing, we asking more in functional requirements. And after interview, we prepared questionaire which is more in interface designing.
The interviewing activity was done by three of our members and while the others will do the documentation and designing.

Dual Music Player That Plays Your MP3 Collection & Your CDs

You want to enjoy your audio CDs while traveling but you also have a huge MP3 collection at home that you want to take with you. The ideal solution? DMP, a portable music player that supports CD and MP3 files. Use the MP3 player as you normally would, hang it around your neck, clip it on your jeans or place it in your pocket. Otherwise open both sides and insert your favorite CD and you got yourself a CD player my friend. Now that’s music to my ears.

Designer: Yong-Seong Kim

Panoramic Digital Camera Spins Like A Top

The next time you wanna capture a good panoramic picture of your vacation in the middle of the Pacific Ocean, put down that tripod and expensive digital camera. Use the Panoramic Digital Camera instead. Just make sure it’s sitting on a level surface, angle it, push a button and watch it spin to take the perfect 360º view of your surroundings. Everything saves to a memory card and yes it’ll do video too. Is it real? No, but it’s a sound concept.

Designer: Hye-Jeong Yang

New Designs

Just want to share with you some new designs which i liked them.
Those are all from " yankodesign.com"

Our WBS

We had choosed Agile Method, which is a new approach of softwre development. Each software development process model have their own project schedule or their own work breakdown structure which is consisting of phases, steps, activities and estimates the time needed for each activities.

Because of the Agile method is less documentation, so our WBS might have less phases than the other groups. We would like to appologize to Pn. Badariah because of the late submission of our WBS. Below is our WBS, please click it to enlarge the graph.

haiii....

im a new member..hehe saje je..bye..

another project progress..

During last class we had on last Thursday,
Pn. Badariah asked us to sit in each group and discuss among us on how our project schedule would be look like..
Therefore, she gave us 15 minutes to discuss..and she said that we required to upload our project schedule into our blog for the developers views and for the clients view which is for this project, our clients is Pn. Badariah..
So, we'll upload our project schedule in here around this week..be patient yaa..hehe

Class on Thusrday, 2 August 2007

Chapter 3: Planning and Managing the Project

In this chapter, we will look at:

• Tracking Progress


• Project porsonnel and organization


• Effort and schedule estimation


• Risk management


• Using process modeling with project planning

I'll explain more in Tracking Progress.

Tracking Progress

A typical projects begins when a client approaches the developers to discuss a perceived need. This is during the Requirements Analysis phase in any software process models. This phase will lead to a design phase because design phase depends on the needs of certain customer. To meets with their requirements, a well-thought-out Project Schedule will be needed.

A Project Schedule is to describes the software-development cycle for a particular project by enumerating the phases or stages of the project and breaking each into discrete tasks or activities to be done. It also potrays the interactions among the activities and estimates the times that each activity will take.

To determine the project schedule, we will begin by working with customers and potential users to understand what they want and need. At the same time, we make sure that they are comfortable with our knowledge of their needs. During project development, the customer also take part of it. They will expects to see the deliverables which is the documents, demonstration of function, demonstrations of subsystems, demonstration of accuracy and the demonstration of reliability,security or performance of the project. To produce this deliverables, the developers must determine milestones and what the activities, what must happend and which activities depend on other activities,products or resources. A milestone is the completion of an activity - a particular point in time.

Project development can be separated into a succession of phases which are composed of steps, and each step can be subdived further into activities if necessary. Below is the graph of the project schedule.