Emily owns this blog which is supposedly Maxinne's.
This blog is also supposedly for schoolwork. Well you know what. That is a load of sheep poo because, yeah, no.
Sorry Sir. (:

Development Methodology.
Note: T_T;;; editted this post before..full had information...but then apparently it didn't post :\ there goes an hour worth of notes -.-;; gah.

System Development Methodology:
> As a noun: framework that is used to structure, plan, and control the process of developing an information system. This structure affects pre-definition of specific aspects that are created and completed by developers in order to create or maintain an application. One method may not be suited to all kinds of prjects, each framework are best suited to specific projects - it's usability depending on various technical, organizational, project and team consideration. Examples of frameworks include:

• Rational Unified Process - since 1998
• Agile Unified Process - since 2005 by Scott Ambler
• Integrated IT Methodology - since 2007

As a verb: an approach used to apply the software framework, and the main approaches are:

• Waterfall: Sequential development approach (linear framework) where development flows steadily downwards through phrases of requirements analysis, design, implmentation, testing (validation), integration, and maintenance. Basic principles involve:
  > Division of phrases - with some overlap and splashback
  > Planning - time schedules, target dates, budgets and implemenation of an entire system at one time
  > Maintenance of control - extensive written doucmentation, as well as formal reviews and approval/signoff by mangaging developer at the end of each stage.
• Prototyping: Creation of prototypes (no surprise there...) and basic principles are:
  > Handling selected portions - not a standalone, complete development
  > Attempts to reduce inherent risk - breaking project into smaller segments and providing more "ease-of-change" during development
  > High user involvement- increase likelhood of user acceptance of the final implementation
  > Small scale mock-ups
  > Basic understand of fundamental business problem - to avoid the wrong problem
• Spiral: Combining elements of both design and prototyping in stages, basic principles are:
  > Focus on risk assessment - minimizing project risk through breaking project into smaller portions
  > "Each cycle involves a progression through the same process of steps..." - each stage has its own elaboration, showing in detail the parts of the project
  > Four basic qudrants - 1: Determine objectives, alternatives and constraints 2: Evaluate alternatives, idenify and resolve risks 3: Develop and verify deliberables 4: Plan the next stage
• Rapid Application Developlment (RAD): Involves iterative development and uses the construction of prototypes. Basic principles:
  > Fast development and delivery, with high quality and low cost
  > Reduce project risks - breaking the project down
  > Emphasis on fulfilling bussiness need - technological or engineering excellence is of lesser importance
  > Joint Application Development (JAD) - users are involved in system design, either through consesus in workshops, or electronically operated interaction
  > Produces documentation necessary to support future development and maintenance

Agile Software Development

A group of software development methodologies, where requriements and solutions evolve through collaboration between self-organizing cross-functional teams (group of people with different expertise working toward a common goal). Generally promote a disciplined project management process that encourages frequent inspection and adpation, a leadership philosphy that encourages teamwork, self-organization and accountability.

There are numerous agile development methods, however most promote development, teamwork, collaboration and process adaptability throughout the life-cycle of the project. They break tasks into small portions with minimal planning, and do not irectly involve long-term planning.

Iterations are short time frames that typically last for one to four week, and each part involes a team working through a full software development cycle including planning, requirements analysis, design, codingm unit testing, and acceptance testing when product is demostrated to stakeholders.

Agile Software Development methods are fall in the 'adaptive' side of developments, and so concentrate on adapting quickly to changing realities, there when the needs of a project change, an adaptive team changes as well. In contrast the 'predictive' methods focus on planning the future in detail, therefore team members would be able to report exactly what features and tasks are planned for the entire lenght of the development process.

An iterative development model

Emily is cool. <- look here (:

Labels: multimedia, notes