Week 7

Like every lecture nowadays i find it confusing and too brief. Once again i ended up reading the study guide during lecture to understand what was being taught this week. In the middle of my reading i was also involved in a conversation with my classmate as boredom and sleepiness was creeping into me.

I just felt SUPER ... Relieved after submitting my Assignment 1a, it was only 5% but the thought and time that went it to doing it was just like an Assignment worth 10% or 15%. I wonder how Assignment 1b would be.... anyways still got a little time to do it.... ;)..... For now i just need to focus on what needs to be learned this week.

Our lecture title was "Finishing Analysis"..... Initially i thought we actually finished the analysis part and were going to start design from next week onwards and i was right.

Finished Analysis basically tells about the last 3 activities of analysis
1) Prioritize system requirements
2) Generate and evaluate alternatives
3) Review Recommendation with management

Prioritizing requirements is based on scope and level of automation. While implementation alternatives are generated and evaluated on key criterias such as: strategic plan, economic feasibility, schedule and resource feasibility, technology feasibility and operational, organizational and cultural feasibility. They also include building system in-house, or buying packaged solution or contracting with a vendor. Take note that while choosing a vendor a trial version of the software solution is installed , observed and benchmarked before deciding on having a contract with the vendor.

Once the alternatives have been selected the last stage is done which is to compile and organize a professional document or report which has an introduction & background on company, states all types of requirements (general, functional, and technical), details for submitting proposal, evaluation criteria & process and requested provider and project information that would be submitted to the executive steering committee or senior management for approval.

One more thing i forgot that this week's lecture was too brief so some parts of week 6 were revised mainly the use case diagram since we were going to do it in tutorial class later. Last week, we did not have the books so we did not start on class diagrams and use cases yet. Hopefully today would be a good exercise in tutorial.

THREE HOURS LATER.........

Time for tutorial class.... our tutor smartly printed the questions for tutorial because like last week some students bring their books..... luckily i brought my book so i could refer to topics that i was not sure about. So i had my first hands-on experience of making class diagrams and use cases and i felt it was "do-able." As i progressed towards the next questions of the tutorial the degree level for making the diagrams was getting harder which is in a way a good practice but it meant more time to do it and sadly i ended up not finishing it during the allocated tutorial time.

On the whole, the day started with relief and ended with relief so a happy day for me. The lecture started off as a blurry concept but the study guide helped understand that this material helps me do my Assignment1b which is about making a report stating the system requirements of CyberRoo and making the diagrams which were taught in the tutorial.

Now a feedback from my lecturer and tutor to know about my progress on Assignment1a awaits me next week and i hope i made good progress.... so i can work on Assignment1b as soon as possible.....

........... LOTS TO DO!.... in LESS TIME....

............OMG! .... week 9 is not far away....