Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Case tools details is fully given in the above books
Typology: Essays (university)
1 / 48
This page cannot be seen from the preview
Don't miss anything!
David Garmire 15-413 Software Engineering Fall 1998 2 15-
Technische Universitaet Muenchen Institut fuer Informatik
David Garmire 15-413 Software Engineering Fall 1998
❖
Typical components of CASE tools ❖
Lifecycle support Roundtrip engineering ❖
The windows of Together/J Creating and modifying class diagrams Handling complexity with packages Code and documentation generation
David Garmire 15-413 Software Engineering Fall 1998
❖
browsing and editing with a graphical user interface automatic code generation documentation generation ❖
persistent storage of all development documents integrated version control system concurrent, distributed modeling ❖
software development tools process and workflow modeling tools offering a scripting language
David Garmire 15-413 Software Engineering Fall 1998
❖
Analysis Design Implementation Testing Maintenance
David Garmire 15-413 Software Engineering Fall 1998
Poor Moderate Good Excellent Activity Requirements definition Formal specification Quality of support (according to Ian Sommerville) Functionoriented design Data modeling Object-oriented design Programming Testing Maintenance Management
David Garmire 15-413 Software Engineering Fall 1998
❖
separate CASE tools exist for different parts of the softwareengineering activities each tool has its own set of project documents and a uniqueuser interface the user works with multiple tools ❖
all tools are working on the same project documents a tool can trigger activities of other tools (e.g. start an formalintegrity check after a model has been changed) the tools share one common user interface the user has the feeling of working with one tool
David Garmire 15-413 Software Engineering Fall 1998
❖
complex functionality confusing user interfaces ❖
one notation one language ❖
“merging” of models is poorly automated ❖
CASE tools belong to the most expensive tools in SE CASE tools require high administration effort
David Garmire 15-413 Software Engineering Fall 1998
❖
❖
Many project management problems are not amenable toautomation. CASE systems are still not integrated. Adopters of CASE technology underestimated the trainingand process adaptation costs.
David Garmire 15-413 Software Engineering Fall 1998
❖ Reverse engineering is therecreation of an analysis ordesign model from existingcode. ❖ Typical flow of events Scan a set of already existingsource code files Generate the object modelfor these files Allow now modifications onthis object model public class Staff extends Employee { ....... } public class Professor extends Employee { ....... } Employee Staff Professor
David Garmire 15-413 Software Engineering Fall 1998
Reverse Engineering Forward Engineering Object Model Code public class Staff extends Employee { ....... } public class Professor extends Employee { ....... } Employee Staff Professor public class Slave extends Employee { ....... } public class Master extends Employee { ....... } Slave Master
David Garmire 15-413 Software Engineering Fall 1998
❖
means analyzing existing software with the purpose ofunderstanding its design and specification. may be part of a reengineering project but may also be used torespecify a system for reimplementation. ❖
means restructuring or rewriting parts or all of a legacysystem without changing its functionality. involves adding effort to make it easier to maintain. Thesystem may be restructured and redocumented.
David Garmire 15-413 Software Engineering Fall 1998
David Garmire 15-413 Software Engineering Fall 1998
❖
class diagrams sequence diagrams collaboration diagrams use case diagrams state transition diagrams ❖
Graphically: by drawing lines (associations, ...), rectangles(classes, packages, ...) in the diagram pane. Menu-based: by selecting an entity in the diagram pane andusing the options in the inspector pane to change itsproperties.
David Garmire 15-413 Software Engineering Fall 1998
❖
❖
which models should be created for PAID how are the models organized (e.g. by subsystems) where are the models stored who is allowed to access different models selection of a configuration management system
