Happy Birthday to me!!!

hehehe....
me growing up now.....

~HAPPY BIRTHDAY TO ME!!!

(^_^)

<-----this present i give to myself....sound weird huh???

31st January

j A j A

Did some work for the portal last night at Shafiqah's. Also picked the template for the portal, and how I wish we could afford the cooler one. Why they have to be so expensive ah? We just download the ones that are free ^^;;

Gotta continue with the project later this afternoon[evening?].

p/s the journey back from I2 to I5 at 1 in the morning can be really scary *__*

The assignments just keep on coming.


And I just keep telling myself to 'Breath in, breath out.. Sabarrrrr [be patience]..' or else I'll probably lose my mind. 0__0

Yep, we need our mind to work properly in order to do our work. =P

Report

Past Report

Date: Tuesday, January 16th 2006
Time: 10-11.45 p.m.
Venue: Fazliza's and Fatihah's house
Members: Fazliza, Fatihah, Syafiqah, Aina

We meet again to discuss about the WBS chart that we did earlier. After discussing with Mdm Badariah after the class, it turns out that it have errors so we had to fix it. Luckily it's not that much, even though there's a few times we almost burst our head off thinking of the right terminology to use.

On Wednesday [January 17th], we went to Mdm Badariah's office to hand out the newly-made chart [sort of], but then we remember that she had to study for her research like she mentioned a day earlier. That's right, she even had a 'Do Not Disturb' sign on her door. We took a peek and she's indeed a bit busy with her work. Not wanting to disturb her, we just put the chart under her door and dashed out like a criminal for no reason. Perhaps we're afraid that she might noticed it..

We hope she won't mind.. and hopefully she didn't step on the chart.

Group Meeting

Date: Monday, January 15th 2007
Time: 10.30 p.m. - 12.15 a.m.
Location: Fazliza's and Fatihah's house
Members: Fazliza, Fatihah, Syafiqah, Aina

Meeting was held at Fazliza/Jaja's and Fatihah's house to discuss about the task that was given by Mdm Badariah in class on Monday. We discussed about the plans that we'll use to build our project, using the Waterfall Model as the example. Another discussion will be held on Tuesday with our team leader Hossein.

*~HaPpY bEsDaY FaTiHaH~*

hepi besday to u....
happy bufday to u....
hapi birthday to FATIHAH....
hapie besday to u.......................................

may ALLAH bless u....


by j A j A

Still preparing for the presentation. I hope Hossein's doing his own preparation as well, since one of us we'll be presenting. Had to discuss more on YM with him later..

Argh, I'm really nervous. Mdm Badariah said if we failed to answer her question, she'll deduct our marks. T___T


.. Wait, how many marks we'll get in the first place?

busy life..!!!~

assignment..quiz..study..huh!!

Beep! Beep! Poseur alert!

If you've been reading messages in our chatbox, you'll noticed that our 'lecturer' had left a not-so-nice [IMO] message telling us to meet her since our blog is 'so bad'. Imagined the shock that we had reading it, and apparently we're not the only group that got message from 'her'. The other 2 groups with chatbox also got the message, and one of them even got a message saying that they should meet her since their blog is so 'lousy'. Heck, I didn't know if our lecturer has a bad taste since I thing that group's blog is just fine.

So off we go to Mdm Badariah's office with mixed feelings; embarrassment, fear, anger[?!] etc And when we told her about 'her message'..


'HUH?'

I thought she already forgot about it so we repeat it, 'You left a message, telling us to come and see you regarding our blog'.

Her reply?

'What message'? And from the look on her face, it is clear that she's really clueless about it. Apparently, it was NOT her who left all those messages, which means somebody had use her name to write it. Since anyone can leave a message using any name, it is hard to know whether it's the real person or not. We're not too sure how to deal with this. We've already disabled anonymous commenting for our blog entries, and for the chatbox? *sigh* Dunno whether we should delete it or just keep it..

Desicions, desicions...


p/s One funny thing when Mdm Badariah read the message left by the poseur in the chatbox, she said, 'Hmmm, my English is definitely not this bad..'


PWNED! =D

*-*just for our knowledge*-*

Chapter 2-Software Development Life Cycle Models
The General Model
Software life cycle models describe phases of the software cycle and the order in which those phases are executed. There are tons of models, and many companies adopt their own, but all have very similar patterns. The general, basic model is shown below:

General Life Cycle Model

Each phase produces deliverables required by the next phase in the life cycle. Requirements are translated into design. Code is produced during implementation that is driven by the design. Testing verifies the deliverable of the implementation phase against requirements.

Requirements
Business requirements are gathered in this phase. This phase is the main focus of the project managers and stake holders. Meetings with managers, stake holders and users are held in order to determine the requirements. Who is going to use the system? How will they use the system? What data should be input into the system? What data should be output by the system? These are general questions that get answered during a requirements gathering phase. This produces a nice big list of functionality that the system should provide, which describes functions the system should perform, business logic that processes data, what data is stored and used by the system, and how the user interface should work. The overall result is the system as a whole and how it performs, not how it is actually going to do it.

Design
The software system design is produced from the results of the requirements phase. Architects have the ball in their court during this phase and this is the phase in which their focus lies. This is where the details on how the system will work is produced. Architecture, including hardware and software, communication, software design (UML is produced here) are all part of the deliverables of a design phase.

Implementation
Code is produced from the deliverables of the design phase during implementation, and this is the longest phase of the software development life cycle. For a developer, this is the main focus of the life cycle because this is where the code is produced. Implementation my overlap with both the design and testing phases. Many tools exists (CASE tools) to actually automate the production of code using information gathered and produced during the design phase.

Testing
During testing, the implementation is tested against the requirements to make sure that the product is actually solving the needs addressed and gathered during the requirements phase. Unit tests and system/acceptance tests are done during this phase. Unit tests act on a specific component of the system, while system tests act on the system as a whole.

So in a nutshell, that is a very basic overview of the general software development life cycle model. Now lets delve into some of the traditional and widely used variations.

Waterfall Model
This is the most common and classic of life cycle models, also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed in its entirety before the next phase can begin. At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. Unlike what I mentioned in the general model, phases do not overlap in a waterfall model.

Waterfall Life Cycle Model
Advantages
>>Simple and easy to use.
>>Easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.
>>Phases are processed and completed one at a time.
>>Works well for smaller projects where requirements are very well understood.

Disadvantages
>>Adjusting scope during the life cycle can kill a project
>>No working software is produced until late during the life cycle.
>>High amounts of risk and uncertainty.
>>Poor model for complex and object-oriented projects.
>>Poor model for long and ongoing projects.
>>Poor model where requirements are at a moderate to high risk of changing.

V-Shaped Model
Just like the waterfall model, the V-Shaped life cycle is a sequential path of execution of processes. Each phase must be completed before the next phase begins. Testing is emphasized in this model more so than the waterfall model though. The testing procedures are developed early in the life cycle before any coding is done, during each of the phases preceding implementation.

Requirements begin the life cycle model just like the waterfall model. Before development is started, a system test plan is created. The test plan focuses on meeting the functionality specified in the requirements gathering.

The high-level design phase focuses on system architecture and design. An integration test plan is created in this phase as well in order to test the pieces of the software systems ability to work together.

The low-level design phase is where the actual software components are designed, and unit tests are created in this phase as well.

The implementation phase is, again, where all coding takes place. Once coding is complete, the path of execution continues up the right side of the V where the test plans developed earlier are now put to use.

V-Shaped Life Cycle Model

Advantages
>>Simple and easy to use.
>>Each phase has specific deliverables.
>>Higher chance of success over the waterfall model due to the development of test plans early on during the life cycle.
>>Works well for small projects where requirements are easily understood.

Disadvantages
>>Very rigid, like the waterfall model.
>>Little flexibility and adjusting scope is difficult and expensive.
>>Software is developed during the implementation phase, so no early prototypes of the software are produced.
>>Model doesn’t provide a clear path for problems found during testing phases.

Incremental Model
The incremental model is an intuitive approach to the waterfall model. Multiple development cycles take place here, making the life cycle a “multi-waterfall” cycle. Cycles are divided up into smaller, more easily managed iterations. Each iteration passes through the requirements, design, implementation and testing phases.

A working version of software is produced during the first iteration, so you have working software early on during the software life cycle. Subsequent iterations build on the initial software produced during the first iteration.

Incremental Life Cycle Model

Advantages
>>Generates working software quickly and early during the software life cycle.
>>More flexible – less costly to change scope and requirements.
>>Easier to test and debug during a smaller iteration.
>>Easier to manage risk because risky pieces are identified and handled during its iteration.
>>Each iteration is an easily managed milestone.

Disadvantages
>>Each phase of an iteration is rigid and do not overlap each other.
>>Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.

Spiral Model
The spiral model is similar to the incremental model, with more emphases placed on risk analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A software project repeatedly passes through these phases in iterations (called Spirals in this model). The baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each subsequent spirals builds on the baseline spiral.

Requirements are gathered during the planning phase. In the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is produced at the end of the risk analysis phase.

Software is produced in the engineering phase, along with testing at the end of the phase. The evaluation phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral.

In the spiral model, the angular component represents progress, and the radius of the spiral represents cost.

Spiral Life Cycle Model

Advantages
>>High amount of risk analysis
>>Good for large and mission-critical projects.
>>Software is produced early in the software life cycle.

Disadvantages
>>Can be a costly model to use.
>>Risk analysis requires highly specific expertise.
>>Project’s success is highly dependent on the risk analysis phase.
>>Doesn’t work well for smaller projects.


And that’s it. If you have any input, especially your views on advantages and disadvantages of any particular model, feel free to leave them in the comments and I can add them to my copy.

Meeting

Just held our first meeting at COIT lobby at 5 p.m. today regarding of our SE assignment. We discussed about which models that is suitable for the Piccadily Television Advertising System. We decided to search more info about the models and in the end compare them to pick out which one is suitable for the system. Each of us were given a type of model and we'll look out for more info about it. We'll have the meeting again of Friday, January 12th.

Waiting for Hossein, but he already arrived at the moment this pic was taken.

Group pic

Meeting dismissed at 5.45 p.m.

uHmm**

this week in SE class, 1st of all sorry to say coz i did't pay attension..i don't know why..maybe coz i dont understand that subject very well..hehe mcm mne nk phm klo buku pun x bace..
as usual when Pn.Badariah ask question to us..all people keep quite and so blurr..just certain people only answer her question..huhuhu

this week we learn chapter 2-Modeling the Process and Life Cycle.
we learn abt process,SPM(software Process Models)...etc

owhh so tired to memorized them..so many model we kne igt..waterfall model,V model, prototyping model...etc.

ermm she also give assignment to us..waaaa
assignment!!
assignment!!

dont forget this assignment k..next monday we will present..huhuh

k la..nak tido..nak tido..


ika

i'm LATE!!!

after shalat subuh me going under the comforter again hug my lovely teddy[chocho]....
Zzzzz (~.~)
sharp 7 a.m my alarm rang.....tottt....tottt....tottt...
i off it!!! Arrgghhh...kacau aje!!! i wanna to sleep la.....
then...."bagai bintang d surga...." my handphone ringing...
hellooo...with my tried voice.
"jaja tak nak pegi kelas ker???" voice in my phone.
then i look up my watch....it 7.45 am already!!
my class start at 8 am
arrghhhh......run to the bathroom and having my bath...me tak mandi kamben k!!!
then i brush my teeth, wear what ever shirt and i'm ready to go class....(",)
i just take 15 minute to ready everything....Amazing huh???
it is fast!!!

enough story my day....
today we doesn't having our group meeting for our first discussion about our first assignment.
we will meet tomorrow at 5 pm. vanue is as usual k guys....
who have SE text book please bring tomorrow k...
me doesn't buy yet larr....
because me don't have my loan yet for this semester lorrr.....poor me (T.T)
ika please borrow me your book please.....hehehehe(^___^)


post by j A j A

~morning

salam..
morning everyone...(",)
just to say hello....heheh

k daaaa

ika

Assignment......

alamakkkk......we have assignment laaa.....
today Puan Badariah has given us assignment....
huhuhuhu.....
what topic huhhh...?
what must we do?
sorry i didn't pay attention.....
it coz mb i not feeling well today...
i feel sooooo cold but my body tempreture sooooo HOT!!!
hurmm.....
is it because of the rain???
huhuhu....is it i nak demam???
uuuwwaaa (T___T)
i want my makkkk.....

so tomorrow we have the meeting tau....
i will ask our leader which is the one and only gentalman in our group the time and place where the meeting is k....

powered by j A j A

eDiT...EdIt..

weeee...(",)
having fun with editing the blog..
now i know what the feeling having a blog..
we can edit......
can add follow our own creativity......
write what we feeling....and such.....

today i just add a link list and chatroom at this blog....
after this i will explore what can i do with this blog to make it more fun and interesting....

-fatihah-

*~cHaT RoOm~*

Salam....
hehehehe....
soooooo.....happy!!! (^____^)
at last we did it create the chat room at our blog....
not so nice...but it our good try to edit something at our blog to make it look interesting...
me as known as jaja and fatihah try our best to create this chat room...hehehehe.
so u guys can join the chat room and have a chit chat with us k.... (*_*)

sorry for my broken english...huhuhu(T_T)

The passing of a great man..

[Music: [tatoeba]kimi...ga...shinda...ra - D'espairsRay]
[Mood: blank .____. ]

The inventor of probably one of the greatest invention is no longer with us.

Momofuku Ando passed away at the age of 96 in Tokyo on Friday. He was the inventor of instant noodles, a snack that have been sold billions of serving worldwide since its launch.

In my opinion, his invention is almost as important as the invention of telephone by Alexander Graham Bell of the lightbulb by Thomas Edison. 'WHY?', you ask?

Let's see, Considering that the ones who'll read this entry are students [Mdm Badariah doesn't count, of course =P], imagine if he didn't create the instant noodle in the first place, can you imagine how we'll survive without it? All of us must at least once, turn to instant noodles [that Maggi for you, or what other brands that you prefer] whenever we're on tight budget. We're students, of course, and it's not uncommon for us to be short on money for some occasion. There's always other options, but usually the first thing that come to mind whenever our stomach starts grumbling [sp?] with be these dudes. And off to the cupboard in the kitchen we go~


[Hmm.. I think we usually short on money because we spend them on other things especially for entertainment, rather than for educational purpose. Or maybe that's just me]


Okay, then, enough rambling. I'm outta here, but not before posting a pic..






p/s I really don't know what possessed me to took that pic above... Oh well. And Mdm Badariah, we'll promise to post our pics soon. I keep forgetting about it.


This is Aina, off to sleep now to get ready for possibly 9 hours of torture... *cough* I mean, lecture on Monday.