cis 3060 midterm 1 study guide + textbook

systems development life cycle (SDLC)

process of developing an info system that supports business needs

development methodology

approach to implementing the SDLC

structured design

formal step by step approach to the SDLC that moves logically from one phase to the next

phased development

breaks the system into a series of versions that are developed sequentially; consists of the implementation of a subset of the requirements

prototyping

development centers on refining a system prototype over several cycles

system prototype

consists of a rudimentary implementation of the system; used in prototyping

object oriented systems analysis and design (OOSAD)

organizes requirements around objects, which integrate behaviors (processes) and data modeled after real world entities with which the system interacts

agile development

methodologies focused on addressing changing requirements instead of detailed development processes, all inclusive documentation, and detailed plans; based on agile manifesto

scrum, extreme programming

2 popular agile frameworks that focus on delivering finished products fast within a transparent culture

scrum

encourages teams to learn through experiences, self organize while working on a problem, and reflect on their wins and losses to continuously improve

extreme programming

focuses on appropriate engineering practices for software development, such as testing and efficient coding practices; code is tested frequently and placed into an integrative testing environment

business value

the benefits obtained from the system; essential to explain when justifying the development of a new info system

tangible

------ benefit can be quantified and measured easily

intangible

------ benefit results from an intuitive belief that the system provides essential but hard to measure benefits to the organization

system request

a document describing the business reasons for building a system + the value the system is expected to provide

requirements determination

performed to turn a high level explanation of the system stated in the system request into a more precise list of requirements

requirement

a statement of what the system must do or what characteristics it must have

functional quality

the degree to which the system meets the functional requirements

as is system

the current system is also called?

to be system

the new system is also called?

functional

models that describe business processes and the interaction of an info system with its environment; provide an external view of the info system by showing how users view the system rather than the internal mechs by which processes and supporting systems operate

use case

a formal representation of how an info system interacts with its environment

activity diagram

-------- models the behavior in a business process; can be used to model everything from a high level business workflow that involves many dif use cases to the details of an individual use case

use case diagram

-------- illustrates in a simple way the main functions of the system and the different kinds of users that will interact with it; includes use cases that describe major business processes the system performs + actors

problem domain models

activity and use case diagrams are also called --------- ;logically describe the business domain's activities without suggesting how they are conducted (no specific details)

structural (conceptual)

a model that describes the structure of the info that supports the business processes carried out by the system

structural (conceptual)

a model that presents the logical organization of the info without indicating how the info is stored/created/manipulated (the technical details)

object

represents info captured by the system; can be people/places/events

class diagram

a static model that shows the classes and relationships among classes that remain constant over time; includes classes/attributes/behaviors

class

a template used to create objects (specific instances) in the problem domain; all objects within are identical in structure and behavior but contain different data in their attributes

problem domain

-------- refers to the business areas affected by the info system

attribute

an ------- defines the structure of the class; represents piece of info or state relevant to the description of the class within the problem domain

operation

an -------- defines the behavior of an analysis class; should be problem domain-specific to the class

functional

activity and use case diagrams are considered ------ modeling

structural (conceptual)

class diagrams are considered ------ modeling

planning

the ------ phase is the WHY? an info system should be built

addresses business value, feasibility

includes system request, project initiation, project management

analysis

the ------- phase is the WHAT? (user pov)

addresses what requirements, what the system will do, what it will have

includes analysis (as is --> to be), requirements gathering, system proposal

design

the ------- phase is the HOW? (developer pov)

addresses how the system will operate

includes strategy, architecture/interface, program documentation

implementation

the final phase of the SDLC cycle

includes system construction, installation, support plan for post-install

unified modeling language (UML)

a standard set of information system model constructs and notations defined by the Object Management Group