Publication | Closed Access
Using UML and agile development methodologies to teach object-oriented analysis & design tools and techniques
12
Citations
4
References
2003
Year
Unknown Venue
EngineeringDesign ToolsObject-oriented ModelingEducationSoftware EngineeringObject OrientationObject-oriented AnalysisSoftware AnalysisAgile Software DevelopmentSystems EngineeringSoftware Development MethodologiesAgile MethodologiesObject-oriented DesignUml StandardSoftware Development ProcessAgile DevelopmentAgile Development MethodologiesDesignComputer ScienceUml DesignSoftware DesignSoftware DevelopmentProgram AnalysisDevelopment MethodologySoftware TestingBusinessSystems IntegrationObject ModelingData Modeling
Software development is shifting toward object‑oriented environments, driven by platforms such as .Net and J2EE, making it essential to train analysts in OO modeling using UML as the standard. The paper presents a series of classes that teach students to elicit requirements and create UML‑based analysis and design artifacts, including an introduction to object patterns. The curriculum employs agile development practices, provides course models and assessment examples, and aligns learning outcomes with the IS'97 model curriculum.
The world of software development and systems integration continues to evolve into an object-oriented (OO) based environment. The advent of new development platforms such as Microsoft's .Net and Sun's J2EE has accelerated the adoption rate of OO based tools and the object-oriented development paradigm. Tomorrow's workers need to be equipped to describe a world made up of objects - whether the objects are self created or inherited from an existing object framework. In addition to offering OO software development classes, educational institutions must also begin educating analysts to create informative models based on OO principles. The Unified Modeling Language (UML) has emerged as the standard for defining modeling principles and techniques. This paper describes our series of classes that teach students how to elicit requirements and turn them into analysis and design level artifacts based on the UML standard. The classes also teach and use a development methodology which is less methodical and more contingency (agile) based. We also introduce the students into the world of object patterns. Course models and examples of learning assessments are included. The paper also maps the learning outcomes from our classes to those purposed in the IS'97 model curriculum document adopted by ACM, AITP, and AIS.
| Year | Citations | |
|---|---|---|
Page 1
Page 1