Just About IT
25May/100

Agile Unified Process

Agile Unified Process





The Agile Unified Process, or Agile UP, is an ultra-lightweight variant of the Unified Process
(UP) which was developed by Grady Booch, James Rumbaugh and Ivar Jacobson ~ and is
marketed by IBM Rational as the Rational Unified Process (RUP). UP is an extensive
process framework that can be applied to a very wide range of projects and is then adapted
to the requirements of each individual project. (http://www.radtac.co.uk/pdf/AUP.pdf)

Agile UP Phases

  1. Inception Phase
  2. Elaboration Phase
  3. Construction Phase
  4. Transition Phase

Agile UP Disciplines

  1. Model
  2. Implementation
  3. Test
  4. Deployment
  5. Configuration Management
  6. Project Management
  7. Environment

Philosophies

The Agile UP is based on the following philosophies:

1. Your staff knows what they're doing. People aren't going to read detailed process documentation, but they will want some high-level guidance and/or training from time to time. The AUP product provides links to many of the details, if you're interested, but doesn't force them upon you.

2. Simplicity. Everything is described concisely using a handful of pages, not thousands of them.

3. Agility. The Agile UP conforms to the values and principles of the agile software development and the Agile Alliance.

4. Focus on high-value activities. The focus is on the activities which actually count, not every possible thing that could happen to you on a project.

5. Tool independence. You can use any toolset that you want with the Agile UP. The recommendation is that you use the tools which are best suited for the job, which are often simple tools or even open source tools.

6. You'll want to tailor the AUP to meet your own needs.

(http://en.allexperts.com/e/a/ag/agile_unified_process.htm)
25May/100

Software Development Methodology

One part that is so critical in creating an information system is choosing the most appropriate methodology. It must be suitable to the project and so you'll be able to utilize them well. One common problem in selecting a methodology is that some end up selecting a model instead of a methodology.

Model Vs. Methodology


Generally, a model or a framework allows you to understand which project deliverable you should produce on a specific time.  It does not show off what you should do. On the other hand, a methodology as defined by the Treasury Enterprise Architecture Framework a methodology is a documented approach for performing activities in a coherent, consistent, accountable, and repeatable manner. It most likely serve as a  step by step guide for you, towards the end of your project development.

Software Development Methodology are like standards that we can employ to organize, plan, and manage the process of developing an Information System. There are different variety of methodologies available, each of these methodologies possesses its own strenghts and weaknesses. A methodology could be appropriate to a certain project and may not appropriate to another project. A specific methodology is best suited to specific kind of project.
Below are some of the commonly used methodologies that you may consider using on your project:

  • Agile Unified Process
  • Capability Maturity Model Integration
  • Crystal
  • Dynamic Systems Development Method
  • Enterprise Unified Process
  • Essential Unified Process
  • Evo
  • Extreme Programming
  • Feature Driven Development
  • Lean Software Development
  • Microsoft Solutions Framework
  • Open Unified Process
  • Prince2
  • Project Management Body of Knowledge
  • Rational Unified Process
  • Scrum
  • Unified Process
Filed under: Tutorials No Comments
18Apr/102

Simple IT Project Study Guide

Information Technology

As defined at Wikipedia.org, a dissertation or thesis is a document submitted in support of candidature for a degree or professional qualification presenting the author's research and findings. Yet, on the field of IT we usually don't call it a thesis, but rather a Project Study.

When you are taking up IT related course (computer science, information technology, information management, computer programming, etc) you'd most likely need to undergo on a Project Study, lucky enough if you'll do it by group. At first, you'd surely won't have an idea where to start, specifically if your kind professor is so lazy doing the discussions about your project. And so here's what we've got that hopefully would guide you on your project smoothly.

Just a note before you proceed. You really need to consider the time given to you. Time is really Gold, and Time is mana.

After you have enrolled your Project Study, the first thing that you need to do is to create an outline of your project, which will be approved by your Colloquium Professor. Most likely you need to write the following on your Project Study(PS) Outline:

  • Title
  • Background of the Study/Rationale and Objectives (BOS)
  • Statement of the Problem (SOP)
  • Scope of the Study (SOS)
  • Proposed methodology / method and procedures (would also include data gathering instrument

Don't be too worried about those stuff yet, most likely you'll need to have an adviser that would guide and help you to accomplished your project. Be choosy in selecting your adviser, picking the wrong one might give you another year for your course. Pick the one whose familiar with the study that you'll be working on.

Let's go ahead and familiarize the components of your Project Study Outline:

Writing IT Project Study

Title

In almost every document, the title is one of the most important part of the your Project Study. The title gives the readers an idea about the project that you're working on. One important rule is that you need to be very specific on your Title. Your objective is to let the readers have a quick idea about your study just by reading your title.  You may consider reading more about this at http://www.essaytown.com/writing/thesis-title or http://www.ehow.com/how_5719041_make-good-thesis-title.html

Some common topics that you may consider:

  • Faculty Evaluation System
  • Enrollment System
  • Human Resource Information System
  • Voting System
  • Inventory System
  • Payroll System
  • Computer Aided Instruction
  • Examination System

Here are some useful links that you may consider for you to have an idea on the tiltle that you'll be working on.

  • http://www.scribd.com/doc/14259783/150-Sofware-Project-Ideas-for-Students-of-Computer-Science
  • http://www.cityu.edu.hk/lib/digital/studproj/ugrad-CS.htm
  • http://www.projecttopics.info/

Background of the Study

This part is usually long, and would really require you time. What you need on this part is to strengthen and make your study credible with the aid of studies and literature's that supports your study. You may need another chapter to justify your study, so called as the Review of Related Literature.

Writing your BOS entails much work on the process of information collection. You sources may come from the Internet, Journals, Articles, Essay etc. Be sure that they are credible and is published within the past 10 years. To make your Background of the Study efficient, you need to cover the different scope or perspective: Global, National, Regional and Local.

Statement of the Problem

On this part you need to identify the problems that you need to address on your study. Below are examples of usual problems that you need to address:

  1. What are the existing processes...
  2. What are the problems encountered ....
  3. What features will be incorporated.....
  4. What security measures and control measures can be adopted.....


Scope of the Study(SOS)

On this part you need to address the main purpose of your study. The things that you'll cover an won't cover.
The scope defines the research scope and design of your project in different aspects like subjects, objectives, resources, effort, special requirements, users or collaborators, time frame, and issues to which the research is focused. You may use some of the following phrases to express your scope:
The study will cover...
The study will focus on...
The study will consider the…
The study will be designed…
The study will be conducted to...
The study will make use of…
The study will converge on...

Delimitations are restrictions/bounds that you need to impose prior to the beginning of your study to limit or narrow down the scope or range of your study.

Some common phrases that you may use to address your scope are the following:
The study will be limited…
The study will not cover…
The researcher/proponent will limit this study to…

You may also consider reading : < a href=”http://office.microsoft.com/en-us/project/HA011424721033.aspx” title=”Write a Scope Statement”>Write a Scope Statement

Proposed methodology / method and procedures (would also include data gathering instrument

Methodology/Method
You need to choose the proper methodology for your study. As describe by Wikipedia a software development methodology or system development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system.
Each of the available methodologies is best suited to specific kinds of projects, based on various technical, organizational, project and team considerations.
Some examples of methodologies are the following:

  • Agile Model Driven Development (AMDD)
  • Dynamic System Development Method (DSDM)
  • Feature-Driven Development (FDD)
  • Rational Unified Process (RUP)
  • Scrum
  • and more...

Don't worry will have a separate post for this methodologies for you to have a better understanding.

Data Gathering Instruments
Data Gathering is a crucial stage of your study, wherein there are different methods or techniques that you may use to gather the data that you need.
Data Gathering Techniques:

  • Questionnaires
  • Interviews
  • Observation
  • Document Analysis

You may consider reading this site to have a more vivid understanding on the above techniques: http://brent.tvu.ac.uk/dissguide/hm1u3/hm1u3text3.htm


Filed under: Tutorials 2 Comments