Cover Letter

A cover letter is what is sent along with the CV when applying for a job. This letter is what introduces yourself for any position and explains the purpose for writing. Includes highlighting skills and expertise and what you are willing to do for the employer (University of Winsconsin, 2012).

What to include in the cover letter

First paragraph - Should be short and explain briefly the reason as to why you are writing this letter
Second paragraph - Why you think you are suitable for the job position and give a brief description of your academic qualifications and refer to skills listed in the job description.
Third paragraph - In this paragraph you have to write what you hope to do for the compny if you receive the job and mention career goals.
Fourth paragraph - Mention why you are interesting in the job position and convince the employer that you would perform well if you had the position applied for.
Closing the letter - End the letter with "Yours sincerely' and sign you name under it.

(Cahillane, 2012)

According to VirginiaTech (2013),  all cover letters should explain why you are sending a resume to the employer. You should also mention where you heard about the job position and why you are interested. It is necessary to mention to the employer to look at your CV to show more information than what is mentioned in the cover letter. Reflect on your attitude, your motivation and personality.

Format and style

• Single A4 size page with a one inch margin
• Times New Roman, Arial, Calibri - 12 ppt 
• Avoid grammar and spelling mistakes
• Finish the cover letter in three paragraphs
• Write in a positive tone

Referred books/websites  
[Online] Available from: http://writing.wisc.edu/Handbook/CovLetter_what.html

[Online] Available from: http://www.reed.co.uk/career-advice/blog/2012/september/how-to-write-a-cover-letter
[Online] Available from: http://www.careers.monash.edu.au/students-grads/apply-for-a-job/cover-letters.html

http://www.career.vt.edu/jobsearchguide/coverlettersamples.html

Development Methodologies

According to CMS (2008), "A system development methodology refers to the framework that is used to structure, plan, and control the process of developing an information system.". Some of the system development methodologies include Waterfall method, Prototyping, Incremental, Spiral and RAD.

Waterfall method (Linear framework)

Some advantages of the model is that its easy for understanding  easy to manage, and phases are completed one at a time. A weakness in this model is that it's costs, slow and it is hard to respond to a change and any changes that occur later are costly (CMS, 2008). The five phases of the waterfall model in sequential order:

• Requirements specification
• Design
• Implementation
• Integration
• Testing
• Installation
• Maintenance

In this methodology the project is divided into phases one after the other with some overlap and splash back acceptable between phases. The stages in this method are feasibility study, system investigation, system analysis, system design, implementation, review and maintenance. A positive point of that waterfall method is easy for planning, conserves the resources and the progress is measurable. As stated by Deeb (2010), it allows for  departmentalization and managerial control.

Spiral methodology (Combination linear and iterative framework)

According to the research done by Deeb (2010), The spiral model was developed by Dr. Barry Boehm and is an "enhancement of the waterfall mode with risk analysis preceding each phase of the cascade". It is used in large systems for internal development and effective when software are reused. Like the waterfall method, spiral methodology adds feedback to previous stages. 

Based on research by Chapman (2004), "The spiral methodology reflects the relationship of tasks with rapid prototyping, increased parallelism, and concurrency in design and build activities. The spiral method should still be planned methodically, with tasks and deliverables identified for each step in the spiral." 

How to select the best suited life cycle
The waterfall cycle is chosen if the user is aware of the requirements and it they are fixed. The spiral method is selected if there are possible risks in each phase and if the client wants to be aware of the decisions made in the phases.

Categories of methodologies

1. Data oriented design - useful for systems that process a lot of data E.g Banking system
2. Function/process oriented design - to process intensive systems
3. OO Methods - usefull for object oriented programs
4. User oriented design
5. Hypertext methods
6. Web methods- WML
7. Instructional design methods
8. Hybrid methods

Referred books/websites  

[Online] Available from: http://istqbexamcertification.com/what-is-waterfall-model-advantages-disadvantages-and-when-to-use-it/

[Online] Available from: http://www.cms.gov/Research-Statistics-Data-and-Systems/CMS-Information-Technology/XLC/Downloads/SelectingDevelopmentApproach.pdf

[Online] Available from: http://cs.anu.edu.au/student/projects/10S1/Reports/Ahmad%20Deeb.pdf

[Online] Available from: http://www.hyperthot.com/pm_sdm.htm

Date: 10th December 2012

Project Management

A project is a temporary endeavor undertaken to create a unique product or service or a result. In order to make a project successful it has to be well organised, balanced, timely, resourceful and generate results that satisfy customers (Old Dominion University, 2012). According to Barren (2009), a project is temporary and includes start and end dates. The main goal of the project is completing it in the given time frame.

Managing a project includes identifying requirements, establishing clear and practical objectives, balancing competing demands of quality, scope, time and cost (Hutchings, 2011). The main process groups of project management includes:

Phase 01: Initiating

• Identify what needs to be done
• What the project needs to accomplish
• Final project goal, project scope
• Identify customer requirements and other stakeholders

Phase 02: Planning

• Modifying the project scope
• List activities that needs to be done
• Develop a gantt chart to schedule the work and work on a budget for the required resources
• Approval of the project plan

Phase 03: Executing

• Meeting minutes with team members
• Communicating with stakeholders
• Solving problems
• Completing the project plan

Phase 04: Controlling

• Monitoring the plan
• Evaluating project changes requested
• Rescheduling the project when necessary
• Adapting resource levels
• Returning to planning stage

Phase 05: Closing

• Acknowledging achievements and results
• Shutting down operations and disbanding the team
• Learning from project experience
• Review project process and outcomes
• Writing a final project report

According to the Project Management Institute (2013), project management "is the application of knowledge, skills and techniques to execute projects effectively and efficiently". "Project management knowledge draws on nine areas which are Integration, cost, human resources, scope, quality, communications, time, procurement and risk management". For project management there must be skills, tools and processes involved. Skills can enhance the chance of making the project successful and reduce risks. Tools are used by project managers to improve success and different processes are used to monitor and complete the project on time. Example: Time management, risk management, quality management.

Triple constraint

Time, Cost and Scope are the main attributes that must be handled effectively when a project is undertaken in order to complete it successfully. As stated by Haughey (2011), the triple constraint shows that projects must be delivered within cost, on time, meet customer requirements and must meed the scopes that were agreed on.

Referred books/websites  
[Online] Available from: http://www.pmi.org/About-Us/About-Us-What-is-Project-Management.aspx

[Online] Available from: http://www.cs.odu.edu/~cs410/whatisaproject.htm

[Online] Available from: http://cnx.org/content/m31435/latest/

[Online] Available from: http://www.projectmanagement.net.au/project_management

[Online] Available from: http://www.projectsmart.co.uk/understanding-the-project-management-triple-constraint.html

Westland, J. (2003) Project Management Guidebook
[Online] Available from: http://www.thoughtware.com.au/documents/method123-ebook.pdf

[Online] Available from: http://programsuccess.wordpress.com/2011/05/02/scope-time-and-cost-managing-the-triple-constraint/

Date: 26^th November 2012

Week 04 : Day 01

Final Year Project 
This project is the final project done by an undergraduate student. The student is given nine months (33 weeks) to do the project. The work done in FYP is the peak of the students academic achievement  Project should be feasible, useful and balanced. In four months time there will be a midpoint interview where the student must attend with the research completed. The project must be:

• Feasible - it should be completed in the time allocated. A gantt chart is made to record all the work done and the time taken for each task to be completed. The midpoint interview is conducted four months before the submission date where the student must have the research completed and it carries 20% of the marks given to the final grade.
• Useful - the solution proposed must result in a usable method and practical.
• Balanced - Should include both qualitative and quantitative material.

Project proposal

A problem statement is a short descriptions of the selected issue, which includes a vision and the methods that could help to solve the problem.The vision is what effect it will have on the public if it is a macro problem and how solving a micro problem will affect an organisation. The chosen problem should be logical and writing the problem statement ideas must be included from primary and secondary sources. Should include objectives of maximum 4-5 points that will be gained.

The contents that should be included in the proposal are the problem statement based on a macro or micro environment and the selected research area.The objectives given must be time focused, measurable and the change that will be implemented. Next is the research methods used and if the project is feasible academically and technically. Lastly the outcomes, conclusion and recommendations are given.

Primary data - Data collected by the person conducting the investigation. Example: Interviews, Questionnaires.This data is expensive and takes time to collect.

Secondary data/Qualitative sources - This data is not original and is work of other people,much cheaper. and mostly out of date. Example: Reports, Newspapers.

According to Ceptara (2013), The first step to think about when writing a problem statement are the following questions (5 W's)

1. who does the problem affect? (who will face changes once problem is solved)
2. what does it affect (what is the result when it is solved)
3. when does the problem happen/when it needs to be fixed
4. where the problem is happening (type of organisation)
5. why is it essential for the problem to be fixed (what are the advantages)

Project contents

• Abstract - this includes three paragraphs separated into the introduction, problem statement, methods used in the project and what will be achieved at the end of the project and key words that are being used.
• Introduction - Contains the table of contents, table of figures and the table of tables and introduction to the  proposed solution.
• Body 

Chapter 01: Introduction, Problem Statement, Research Question, Aims and Objectives
Chapter 02: Industry Analysis (SWOT, PEST, Value Chain, Porter's Analysis) - External environment
Chapter 03: Academic research (Literature review, Design)
Chapter 04: Initial design specification - Compare and contrast databases (Midpoint interview)
Chapter 05: Design - how it is being developed (ERD, DFD, Use case)
Chapter 06: Testing
Chapter 07: Implementation

• Conclusion
• List of references
• Bibliography
• Appendices

Referred books/websites  

Ceptara (2013) How to write a problem statement
[Online] Available from: http://www.ceptara.com/blog/how-to-write-problem-statement

[Online] Available from: http://curriculum.leeds.ac.uk/rbl/final-year-project