For any human, to have any hope of being successful, it must pass through a small set of essential phases.

Size: px
Start display at page:

Download "For any human, to have any hope of being successful, it must pass through a small set of essential phases."

Transcription

1 CHAPTER 1 Logical Analysis & Problem Solving for Programming Beginning System Analysis and Design For any human, to have any hope of being successful, it must pass through a small set of essential phases. 1. Find out what needs to be done 2. Plan what needs to be done 3. Carry out the plan 4. Evaluate what has been done. System 1. All biological organisms are systems and made up of systems; and all machines are systems. System with feedback 1. feedback : A return of part of the output of a system to the input as a means towards improved quality or selfcorrection of error. 2. Negative and positive feedback. 3. GIGO Garbage In Garbage Out Program working on incorrect data produces incorrect results. Subsystems Systems are generally builtup of smaller systems called subsystems. Systems analysis and design is a systematic approach to: Identifying problems, opportunities, and objectives. Analyzing the information flows in organizations. Designing computerized information systems to solve a problem. Information System A groupware of people, objects and processes that provides information about the organization and its environment. It should be useful to members and clients of that organization. Importance of Information Information is an organizational resource, which must be managed as carefully as other resources. Costs are associated with information processing. Information processing must be managed to take full advantage of its potential. ITDB 3100 Logical Analysis and Problem Solving for Programming 1

2 Categories Information systems fall into one of the following eight categories: Transaction processing systems (TPS). Office automation systems (OAS). Knowledge work systems (KWS). Management information systems (MIS). Decision support systems (DSS). Expert systems (ES) and Artificial Intelligence (AI). Group decision support systems (GDSS) and ComputerSupported Collaborative Work Systems. Executive support systems (EES). New Technologies New technologies are being integrated into traditional systems: Ecommerce uses the Web to perform business activities. Enterprise Resource Planning (ERP) has the goal of integrating many different information systems within the corporation. Wireless and handheld devices, including mobile commerce (mcommerce). Open source software. ITDB 3100 Logical Analysis and Problem Solving for Programming 2

3 History of SDLC Models CHAPTER 2 The Software Development Life Cycle Once upon a time, software development consisted of a programmer writing code to solve a problem or automate a procedure. Nowadays, systems are so big and complex that teams of architects, analysts, programmers, testers and users must work together to create the millions of lines of customwritten code that drive our enterprises. Note: There are different types of software development that call for different development strategies. How Software Engineering has changed Seven factors that have altered software engineering practice: 1. Criticality of timetomarket for commercial products 2. Shifts in the economics of computing: lower hardware costs and greater development and maintenance costs 3. Availability of powerful desktop computing 4. Extensive local and widearea networking 5. Availability and adoption of OO technology 6. GUI s using windows, icons, menus and pointers 7. Unpredictability of the waterfall method of software development To manage this, a number of system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and stabilize. What Is the SDLC? The software/system development life cycle (SDLC) is the overall process of developing information systems through a multistep process from investigation of initial requirements through analysis, design, implementation and maintenance. There are many different models and methodologies, but each generally consists of a series of similar defined steps or stages. ITDB 3100 Logical Analysis and Problem Solving for Programming 3

4 Phases of the SDLC Feasibility study and project planning. Requirements definition and systems analysis. Systems and program design. Implementation. Unit testing, Integration and system testing: Acceptance, installation, deployment. Maintenance. Phases of the SDLC Over the years, one thing that has become apparent to most software engineers is that requirements grow and change throughout the process and beyond. They are not static. This calls for considerable feedback and iterative consultation with the users. Often you will find the need to go back and reiterate earlier stages a number of times as the project progresses. In the SDLC process, some activities obviously can't start before others such as you need a design before you can start coding but there is a considerable overlap between some of the activities. Many argue that the most effective model for dealing with today s systems development is the incremental model. The incremental model divides the product into builds, where sections of the project are created and tested separately. This method also allows many teams to work efficiently in parallel. Teams can do successive compilations (called builds) of the entire project, bringing together all the current components. Tools Used in Phases of SDLC: Project Planning Feasibility study and project planning: In this phase, the project manager establishes a highlevel view of the intended project and determines its goals. The software engineer uses his/her technical expertise to determine the feasibility of the desired goals and to give cost/time estimates. ITDB 3100 Logical Analysis and Problem Solving for Programming 4

5 Usually the project manager and the software engineer(s) meet with the users to generate a highlevel project plan. Gantt charts are often used to track progress in the project plan. As requirements are gathered and specific tasks assigned, this project plan is refined. Popular tools used in this phase: Personnel involved: Microsoft project is the industry standard for maintaining project plans. Analyst User management Systems management Tools Used in Phases of SDLC: Requirements Gathering Requirements definition and analysis: In this phase, the SE refines project goals into defined functions and operations for the intended application. He/she constantly analyzes enduser information needs and transforms this information into models used by the programmers. UML is the standard modeling language used for OO system design. It is a very powerful modeling language and we could spend several semesters just talking about UML alone. We will only learn the basics. Popular tools used in this phase: Rational rose, TogetherJ, EclipseUML. Personnel involved: Analyst User management User operations workers Systems management ITDB 3100 Logical Analysis and Problem Solving for Programming 5

6 Tools Used in Phases of SDLC: System and Program Design System and program design. System and program design are slightly different. In system design, the engineer designs the system components and how they will interact. This includes the presentation layer pieces (e.g. Screen layouts), the business logic layer pieces (business rules), and the data layer pieces (data access processes). The SE will determine what technologies should be used in each layer. Program design is system design at a finer level. Here the flow and structure of the actual program code is specified. For example, senior programmers/analysts will take the UML model and write pseudocode detailing the classes, methods, interfaces, package design, etc. More junior programmers will take this pseudocode and transform it into actual code (e.g. with java). Popular tools used in this phase: Visio is a very popular tool for drawing flow charts and etc. For program design. Rational rose, TogetherJ, and EclipseUML are excellent resources for class diagrams. They all have the ability to transform changes to a UML model into code and viceversa. Personnel involved: Analyst System designer User management User operations workers Systems management Tools Used in Phases of SDLC: Implementation Implementation This is where the real code is written based on the system and program design. IDE s (Integrated Development Environments) provide many helpful tools that assist programmers in this phase of development. Examples of these views include: Varying views, debuggers, code completion, code organization, color schemes, and builtin plugins to help with other phases. ITDB 3100 Logical Analysis and Problem Solving for Programming 6

7 Application Servers are needed to run servlets (Java s version of serverside program). The engineer will write code in the IDE for objects that will execute in the application server. Source code repositories are tools used to manage source code among several developers. They allow developers to check code out (preventing other developers from modifying that program). They also maintain version control allowing developers to see what changes were made by other developers. Popular tools used in this phase: IDE s Eclipse, Visual Café, Visual Age, JDeveloper, Kawa We are going to use Eclipse, which is shareware from the Jakarta project. Eclipse is an IDE that has many plugins for the other tools we will be using. Application Servers: WebLogic, WebSphere, Tomcat Although WebLogic and WebSphere control most of the market in larger companies, most smaller companies use Tomcat, which is shareware from the Jakarta project. All app servers vary in different respects, but almost all work the same way for basic functionality. So, by learning one, it is easier to learn the others. We will use Tomcat because it is an industry standard, it is easier to work with than most app servers, and it is free. Source code repository and version control systems Personnel involved: CVS, ClearCase, PVCS, etc. We are going to use CVS, which is also from the Jakarta project. CVS is an industry leader in SCM tools and is shareware. Analyst System designer Programmers User management User operations workers Systems management ITDB 3100 Logical Analysis and Problem Solving for Programming 7

8 Tools Used in Phases of SDLC: Testing Testing Testing is an extremely important part of system development. Many companies have teams dedicated to testing and QA alone. There are different levels of testing that are needed throughout the SDLC. Unit testing This includes the testing of individual components. You have complete control over the test data and test cases and you run the tests yourself. Integration testing In this stage of testing, the SE often collaborates with a small number of other developers to test the integration of various system components. System testing. Popular tools used in this phase: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. These tests are often performed by a QA team. JUnit is used for unit and integration testing. Personnel involved: This is a very popular tool in the J2EE world. It is free shareware from the Jakarta project. It has the ability to set up testing plans for individual components including regression testing. We will use this for our unit and integration testing. Analyst System designer Programmer Systems management ITDB 3100 Logical Analysis and Problem Solving for Programming 8

9 Tools Used in Phases of SDLC: Deployment Delivery and Deployment This is the final stage of initial development, where the software is put into production and runs actual business. This part of the project is most often done by a build engineer, but software engineers should be familiar with the deployment tools used by the build engineer. The SE will often use the same tool for development and testing. Popular tools used in this phase: Ant, Make We will use Ant, a shareware tool from the Jakarta project. It is an industrystandard in the OO development community. It is free. It is easier to use than Make. It is integrated with Eclipse. Tools Used in Phases of SDLC Maintenance What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever. Most junior developers start here to learn the systems. Popular tools used in this phase: All of the tools above Personnel involved: Analyst System designer Programmers Systems management ITDB 3100 Logical Analysis and Problem Solving for Programming 9

10 Project Initiation CzHAPTER 3 Determining Feasibility and Managing Analysis and Design Activities Projects are initiated for two broad reasons: Problems that lend themselves to systems solutions. Opportunities for improvement through Upgrading systems. Altering systems. Installing new systems. Organizational Problems Identify problems by looking for the following signs: Check output against performance criteria Too many errors. Work completed slowly. Work done incorrectly. Work done incompletely. Work not done at all. Observe behavior of employees High absenteeism. High job dissatisfaction. High job turnover. Listen to feedback from vendors, customers, and suppliers Complaints. Suggestions for improvement. Loss of sales. Lower sales. Project Selection Five specific criteria for project selection: Backed by management. Timed appropriately for commitment of resources. It moves the business toward attainment of its goals. Practicable. Important enough to be considered over other projects. ITDB 3100 Logical Analysis and Problem Solving for Programming 10

11 Possibilities for Improvement Many possible objectives exist including: Speeding up a process. Streamlining a process. Combining processes. Reducing errors in input. Reducing redundant storage. Reducing redundant output. Improving system and subsystem integration. Feasibility Impact Grid (FIG) A feasibility impact grid (FIG) is used to assess the impact of any improvements to the existing system. It can increase awareness of the impacts made on the achievement of corporate objectives Current or proposed systems are listed on the left. Objectives are listed on the top. Red arrows indicate a positive impact. Green arrows indicate implementation. Feasibility A feasibility study assesses the operational, technical, and economic merits of the proposed project. There are three types of feasibility: Technical feasibility. Economic feasibility. Operational feasibility. 1. Technical Feasibility Technical feasibility assesses whether the current technical resources are sufficient for the new system. If they are not available, can they be upgraded to provide the level of technology necessary for the new system. 2. Economic Feasibility Economic feasibility determines whether the time and money are available to develop the system. Includes the purchase of: New equipment. Hardware. Software. ITDB 3100 Logical Analysis and Problem Solving for Programming 11

12 3. Operational Feasibility Operational feasibility determines if the human resources are available to operate the system once it has been installed. Users that do not want a new system may prevent it from becoming operationally feasible. Activity Planning Activity planning includes: Selecting a systems analysis team. Estimating time required to complete each task. Scheduling the project. Two tools for project planning and control are Gantt charts and PERT diagrams. Estimating Time Project is broken down into phases. Further project is broken down into tasks or activities. Finally project is broken down into steps or even smaller units. Time is estimated for each task or activity. Most likely, pessimistic, and optimistic estimates for time may be used. Gantt Charts Easy to construct and use. Shows activities over a period of time. Gantt Chart Example ITDB 3100 Logical Analysis and Problem Solving for Programming 12

13 PERT Diagram PERTProgram Evaluation and Review Technique PERT diagrams show precedence, activities that must be completed before the next activities may be started. Once a diagram is drawn it is possible to identify the critical path, the longest path through the activities. Monitoring critical path will identify shortest time to complete the project. PERT Diagram Example PERT Diagram Advantages Easy identification of the order of precedence Easy identification of the critical path and thus critical activities Easy determination of slack time, the leeway to fall behind on noncritical paths Timeboxing Timeboxing sets an absolute due date for project delivery. The most critical features are developed first and implemented by the due date. Other features are added later. Personal Information Manager Software Personal information manager (PIN) software is useful for scheduling activities and includes features such as: Telephone and fax number lists. Todo lists. Online calendars. ITDB 3100 Logical Analysis and Problem Solving for Programming 13

14 Team Management Teams often have two leaders: One who leads members to accomplish tasks. One concerned with social relationships. The systems analyst must manage: Team members. Their activities. Their time and resources. Goal Setting Successful projects require that reasonable productivity goals for tangible outputs and process activities be set. Goal setting helps to motivate team members. Ecommerce Project Management Ecommerce and traditional software project management differences: Project Failures The data used by ecommerce systems is scattered across the organization. Ecommerce systems need a staff with a wide variety of skills. Partnerships must be built externally and internally well ahead of implementation. Security is of utmost importance. Project failures may be prevented by: Training. Experience. Learning why other projects have failed. Extreme Programming Extreme programming (XP) takes good systems development practices to the extreme. Extreme Programming Variables Extreme programming has four variables that the developer can control: Time. Cost. Quality. Scope. These are balanced for a project. ITDB 3100 Logical Analysis and Problem Solving for Programming 14

15 Extreme Programming Extreme Programming Activities The activities of extreme programming are: Coding. Testing. Listening. Designing. Extreme Programming Core Practices There are four core practices in extreme programming: A short release time. Working a 40hour week. Having an onsite customer. Pair programming. ITDB 3100 Logical Analysis and Problem Solving for Programming 15

16 Roles in Extreme Programming Roles in Extreme Programming There are a 7roles played in XP: Programmer. Customer. Tester. Tracker. Coach. Consultant. Big Boss. The Planning Game The planning game defines rules to help formulate the development team and customer relationship. Limits uncertainty. Two players: the development team and the business customer. Customers decide what to tackle first. ITDB 3100 Logical Analysis and Problem Solving for Programming 16

17 XP Development Process XP projects are interactive and incremental. The five Stages of XP development are: Exploration. Planning. Iterations to the first release. Productionizing. Maintenance. XP Development Process ITDB 3100 Logical Analysis and Problem Solving for Programming 17

18 EXERCISE I : GANTT & PERT 1. Ths systems analysis consulting firm of Flow Associates is working on a systems project for Wind and Waves Surfing Gear, Inc. i. Using the data from the table below, draw a Gantt chart to help Flow Associates organize its design project. Description Task Must Follow Expected Time (Days) Draw data flow P None 9 Draw decision tree Q P 12 Revise tree R Q 3 Write up project S R,Z 7 Organize data dictionary T P 11 Do output prototype X None 8 Revise output design Y X 14 Design database Z T,Y 5 ii. Create a PERT diagram for above data. List all paths, and calculate and identify the ciritical path. 2. Prepare a list of activities for an online travel agent who is setting up a Web site for customer to book a flight, make direct purchases, and choose their own seats. i. On the basis of activities prepare the Gantt chart. ii. On the basis data availbale create a PERT diagram. List all paths, and calculate and identify critical path. 3. A PERT diagram of a company used for Information Gathering users phase. i. From the above PERT diagram fill up following table in proper order. Description Task Must Follow Expected Time (Days) ITDB 3100 Logical Analysis and Problem Solving for Programming 18

19 ii. iii. From above table prepare a Gantt chart. List all the paths and calculate and determine the critical path for the Gathering Information PERT diagram. 4. A PERT diagram of a company used for Interviewing users phase. i. From the above PERT diagram fill up following table in proper order. Description Task Must Follow Expected Time (Days) ii. iii. From above table prepare a Gantt chart. List all the paths and calculate and determine the critical path for the Interview Users PERT diagram. CASEI : ITDB 3100 Logical Analysis and Problem Solving for Programming 19

20 CASEI : CPU CASE ITDB 3100 Logical Analysis and Problem Solving for Programming 20

21 Chapter 4 Analyzing Systems Using Data Flow Diagrams Data Flow Diagrams DFDs are one of the main methods available for analyzing dataoriented systems. DFDs emphasize the logic underlying the system. The systems analysts can put together a graphical representation of data movement through the organization. Advantages of the Data Flow Diagram Approach Four advantages over narrative explanations of data movement: Basic Symbols Freedom from committing to the technical implementation too early. Understanding of the interrelationships of systems and subsystems. Communicating current system knowledge to users. Analysis of the proposed system. Four basic symbols are: A double square for an external entitya source or destination of data. An arrow for movement of data from one point to another. A rectangle with rounded corners for the occurrence of transforming process. An openended rectangle for a data store. Basic Symbols ITDB 3100 Logical Analysis and Problem Solving for Programming 21

22 External Entities Represent people or organizations outside of the system being studied Shows the initial source and final recipient of data and information Should be named with a noun, describing that entity External entities may be: Customer Processes A person, such as CUSTOMER or STUDENT. A company or organization, such as BANK or SUPPLIER. Another department within the company, such as ORDER FULFILLMENT. Another system or subsystem, such as the INVENTORY CONTROL SYSTEM. Represent either: A whole system A subsystem Work being done, an activity 1 Add New Customer 2 Customer Inquiry Subsystem Names should be in the form verbadjectivenoun The exception is a process that represents an entire system or subsystem. Data Stores Name with a noun, describing the data Data stores are usually given a unique reference number, such as D1, D2, D3. Include any data stored, such as: A computer file or database. A transaction file. A set of tables. A manual file of records. D1 Customer Master Data Flow New Customer Customer Record Data flow shows the data about a person, place, or thing that moves through the system. Names should be a noun that describes the data moving through the system. Arrowhead indicates the flow direction. Use double headedarrows only when a process is reading data and updating the data on the same table or file. ITDB 3100 Logical Analysis and Problem Solving for Programming 22

23 Developing Data Flow Diagrams Use the following guidelines: Create the context level diagram, including all external entities and the major data flow to or from them. Create Diagram 0 by analyzing the major activities within the context process. Include the external entities and major data stores. Create a child diagram for each complex process on Diagram 0. Creating Data Flow Diagrams Detailed data flow diagrams may be developed by: Making a list of business activities. Analyzing what happens to an input data flow from an external entity. Analyzing what is necessary to create an output data flow to an external entity. Examining the data flow to or from a data store. Analyzing a welldefined process for data requirements and the nature of the information produced. Noting and investigating unclear areas. Data Flow Diagram Levels Data flow diagrams are built in layers. The top level is the Context level. Each process may explode to a lower level. The lower level diagram number is the same as the parent process number. Processes that do not create a child diagram are called primitive. ContextLevel Data Flow Diagram It contains only one process, representing the entire system. The process is given the number zero. All external entities are shown on the context diagram as well as major data flow to and from them. The diagram does not contain any data stores. Diagram 0 Diagram 0 is the explosion of the context level diagram. It should include up to 7 or 9 processes. Any more will result in a cluttered diagram. Processes are numbered with an integer. The major data stores and all external entities are included on Diagram 0. ITDB 3100 Logical Analysis and Problem Solving for Programming 23

24 Child Diagrams Each process on diagram zero may be exploded to create a child diagram. Each process on a lowerlevel diagram may be exploded to create another child diagram. These diagrams found below Diagram 0 are given the same number as the parent process. Process 3 would explode to Diagram 3. Each process is numbered with the parent diagram number, a period, and a unique child diagram number Examples are: Edit Customer Calculate Customer Discount 3.2 on Diagram 3, the child of process on Diagram 5.2, child of process 5.2. On Diagram 3, the processes would be numbered 3.1, 3.2, 3.3 and so on. External entities are usually not shown on the child diagrams below Diagram 0. If the parent process has data flow connecting to a data store, the child diagram may include the data store as well. A lowerlevel diagram may contain data stores not shown on the parent process, such as: A file containing a table of information (such as a tax table). A file linking two processes on the child diagram. Minor data flow, such as an error line, may be included on a child diagram. An interface data flow is data that are input or output from a child diagram that matches the parent diagram data flow. Processes that do not create a child diagram are called primitive processes. Logic is written for these processes. ITDB 3100 Logical Analysis and Problem Solving for Programming 24

25 Chapter 5 Analyzing Systems Using Data Dictionaries Data Dictionary Data dictionary is a main method for analyzing the data flows and data stores of dataoriented systems. The data dictionary is a reference work of data about data (metadata). It collects, coordinates, and confirms what a specific data term means to different people in the organization. Reasons for Using a Data Dictionary The data dictionary may be used for the following reasons: The Repository Provide documentation. Eliminate redundancy. Validate the data flow diagram. Provide a starting point for developing screens and reports. To develop the logic for DFD processes. A data repository is a large collection of project information. It includes: Information about system data. Procedural logic. Screen and report design. Relationships between entries. Project requirements and deliverables. Project management information. Data Dictionary and Data Flow Diagram ITDB 3100 Logical Analysis and Problem Solving for Programming 25

26 Data Dictionary Contents Data dictionaries contain: Defining Data Flow Data flow. Data structures. Elements. Data stores. Each data flow should be defined with descriptive information and its composite structure or elements. Include the following information: Data Flow Example ID identification number. Label, the text that should appear on the diagram. A general description of the data flow. The source of the data flow This could be an external entity, a process, or a data flow coming from a data store. The destination of the data flow Type of data flow, either: A record entering or leaving a file. Containing a report, form, or screen. Internal used between processes. The name of the data structure or elements The volume per unit time This could be records per day or any other unit of time. An area for further comments and notations about the data flow Name Description Source Destination Type Data Structure Volume/Time Comments Customer Order Contains customer order information and is used to update the customer master and item files and to produce an order record. Customer External Entity Process 1, Add Customer Order Screen Order Information 10/hour An order record contains information for one customer order. The order may be received by mail, fax, or by telephone. ITDB 3100 Logical Analysis and Problem Solving for Programming 26

27 Defining Data Structures Data structures are a group of smaller structures and elements. An algebraic notation is used to represent the data structure. Algebraic Notation The symbols used are: Repeating Groups Equal sign, meaning consists of. Plus sign, meaning "and. Braces {} meaning repetitive elements, a repeating element or group of elements. Brackets [] for an either/or situation. The elements listed inside are mutually exclusive. Parentheses () for an optional element. A repeating group may be: A subform. A screen or form table. A program table, matrix, or array. There may be one repeating element or several within the group. The repeating group may have: Conditions. A fixed number of repetitions. Upper and lower limits for the number of repetitions. Physical and Logical Data Structures Data structures may be either logical or physical. Logical data structures indicate the composition of the data familiar to the user. Physical Data Structures Include elements and information necessary to implement the system Additional physical elements include: Key fields used to locate records. Codes to indicate record status. Codes to identify records when multiple record types exist on a single file. A count of repeating group entries. ITDB 3100 Logical Analysis and Problem Solving for Programming 27

28 Data Structure Example Customer Order = Customer Number + Customer Name + Address + Telephone + Catalog Number + Order Date + {Order Items} + Merchandise Total + (Tax) + Shipping and Handling + Order Total + Method of Payment + (Credit Card Type) + (Credit Card Number) + (Expiration Date) Data Dictionary and Data Flow Diagram Levels Data dictionary entries vary according to the level of the corresponding data flow diagram. Data dictionaries are created in a topdown manner. Data dictionary entries may be used to validate parent and child data flow diagram level balancing. Whole structures, such as the whole report or screen, are used on the top level of the data flow diagram. Either the context level or diagram zero Data structures are used on intermediatelevel data flow diagram. Elements are used on lowerlevel data flow diagrams. ITDB 3100 Logical Analysis and Problem Solving for Programming 28

29 Data Dictionary and Data Flow Diagram Levels Creating Data Dictionaries 1. Information from interviews and JAD sessions is summarized on Input and Output Analysis Forms. This provides a means of summarizing system data and how it is used. 2. Each structure or group of elements is analyzed. 3. Each element should be analyzed by asking the following questions: Are there many of the field? If the answer is yes, indicate that the field is a repeating field using the { } symbols. Is the element mutually exclusive of another element? If the answer is yes, surround the two fields with the [ ] symbols. Is the field an optional entry or optionally printed or displayed? If so, surround the field with parenthesis ( ). 4. All data entered into the system must be stored. Create one database table or file for each different type of data that must be stored. Add a key field that is unique to each table. ITDB 3100 Logical Analysis and Problem Solving for Programming 29

30 Process Specifications Chapter 6 Describing Process Specifications and Structured Decisions Process specifications are created for primitive processes and some higher level processes on a data flow diagram. They are also called minispecs. Goal of Creating Process Specifications The goals of producing process specifications are: Reduce process ambiguity. Obtain a precise description of what is accomplished. Validate the system design, including data flow diagrams and the data dictionary. Process Specifications Process specifications are not created for: Physical input and/or output processes. Processes that represent simple data validation. Processes for which prewritten code already exists. Data Flow Diagram and Process Specifications ITDB 3100 Logical Analysis and Problem Solving for Programming 30

31 Process Specification Example Part 1 Number 1 Name Add Customer Order Description Key and add the Customer Order. The order should be edited for correct information. Customer and Item master files are updated. Input Data Flow Customer Order Form from the Customer Customer Record from data store D1, Customer Master File Item Record from data store D2, Item Master File Output Data Flow Pending Order to data store D3, Order File Backordered Item Record to the Inventory Control Department Updated Customer and Item records Type of process Online Structured English Structured E nglish is based on structured logic and Simple English statements such as add, multiply, move, and so on. It is an appropriate technique for analyzing the system when structured decisions are not complex. Steps to Use Structured English The following steps are needed: Express all logic in terms of sequential structures, decision structures, case structures, or iterations. Use and capitalize accepted keywords such as IF, THEN, ELSE, DO, and PERFORM. Indent blocks of statements to show their hierarchy (nesting) clearly. Underline words or phrases used have been defined in a data dictionary to signify that they have a specialized, reserved meaning. Be careful when using "and" and "or. Avoid confusion when using logical comparisons such as "greater than" and "greater than or equal to. ITDB 3100 Logical Analysis and Problem Solving for Programming 31

32 Structured English Advantages of Structured English Clarifying the logic and relationships found in human languages An effective communication tool, and easy to teach and understand Data Dictionary and Structured English The data dictionary is a starting point for creating structured English: Decision Tables Sequenced data dictionary entries become simple structured English statements. Selection [] entries become IF..THEN...ELSE statements. Iteration { } entries become DO WHILE, DO UNTIL, or PERFORM UNTIL structured English statements. Decision tables provide a way to examine, describe, and document decisions using a table. They are used to: Describe the conditions. Identify possible decision alternatives. Indicate actions should be performed. Describe actions. ITDB 3100 Logical Analysis and Problem Solving for Programming 32

33 Decision Table Format Decision Table Example Decision tables help analysts ensure completeness and accuracy. Four main problems that can occur in developing decision tables: Incompleteness. Impossible situations. Contradictions. Redundancy. ITDB 3100 Logical Analysis and Problem Solving for Programming 33

34 Redundancy and Contradictions Decision Trees Decision trees are used when complex branching occurs in a structured decision process. Trees are also useful when it is essential to keep a string of decisions in a particular sequence. Drawing Decision Trees First, identify all conditions and actions and the order and timing of these (if they are critical). Second, begin building the tree from left to right while making sure you are complete in listing all possible alternatives before moving over to the right. Decision Tree Example Decision Tree Advantages Three advantages over a decision table are: The order of checking conditions and executing actions is immediately noticeable. Second, conditions and actions of decision trees are found on some branches but not on others. Third, compared to decision tables, decision trees are more readily understood by others in the organization. ITDB 3100 Logical Analysis and Problem Solving for Programming 34

Project Management. Systems Analysis and Design, 8e Kendall & Kendall

Project Management. Systems Analysis and Design, 8e Kendall & Kendall Project Management Systems Analysis and Design, 8e Kendall & Kendall Learning Objectives Understand how projects are initiated and selected, define a business problem, and determine the feasibility of

More information

Chapter 8 Approaches to System Development

Chapter 8 Approaches to System Development Systems Analysis and Design in a Changing World, sixth edition 8-1 Chapter 8 Approaches to System Development Table of Contents Chapter Overview Learning Objectives Notes on Opening Case and EOC Cases

More information

ONLINE SUPPLEMENTAL BAPPENDIX PROJECT SCHEDULES WITH PERT/CPM CHARTS

ONLINE SUPPLEMENTAL BAPPENDIX PROJECT SCHEDULES WITH PERT/CPM CHARTS ONLINE SUPPLEMENTAL BAPPENDIX PROJECT SCHEDULES WITH PERT/CPM CHARTS Chapter 3 of Systems Analysis and Design in a Changing World explains the techniques and steps required to build a project schedule

More information

D6 INFORMATION SYSTEMS DEVELOPMENT. SOLUTIONS & MARKING SCHEME. June 2013

D6 INFORMATION SYSTEMS DEVELOPMENT. SOLUTIONS & MARKING SCHEME. June 2013 D6 INFORMATION SYSTEMS DEVELOPMENT. SOLUTIONS & MARKING SCHEME. June 2013 The purpose of these questions is to establish that the students understand the basic ideas that underpin the course. The answers

More information

Introduction to Systems Analysis and Design

Introduction to Systems Analysis and Design Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.

More information

LECTURE 11: PROCESS MODELING

LECTURE 11: PROCESS MODELING LECTURE 11: PROCESS MODELING Outline Logical modeling of processes Data Flow Diagram Elements Functional decomposition Data Flows Rules and Guidelines Structured Analysis with Use Cases Learning Objectives

More information

Subject : System Analysis and Design BCA -II UNIT 1

Subject : System Analysis and Design BCA -II UNIT 1 Subject : System Analysis and Design BCA -II UNIT 1 Ques1 what is system design.explain its types. Ans: SYSTEM DESIGN :Systems design is the process or art of defining the architecture, components, modules,

More information

(Refer Slide Time: 01:52)

(Refer Slide Time: 01:52) Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This

More information

11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java. What is Project Management?

11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java. What is Project Management? 11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process Project management encompasses all the

More information

How To Design An Information System

How To Design An Information System Information system for production and mounting of plastic windows MARCEL, MELIŠ Slovak University of Technology - Faculty of Material Sciences and Technology in Trnava, Paulínska 16 street, Trnava, 917

More information

SOFTWARE ENGINEERING INTERVIEW QUESTIONS

SOFTWARE ENGINEERING INTERVIEW QUESTIONS SOFTWARE ENGINEERING INTERVIEW QUESTIONS http://www.tutorialspoint.com/software_engineering/software_engineering_interview_questions.htm Copyright tutorialspoint.com Dear readers, these Software Engineering

More information

Software Engineering. What is a system?

Software Engineering. What is a system? What is a system? Software Engineering Software Processes A purposeful collection of inter-related components working together to achieve some common objective. A system may include software, mechanical,

More information

Information Management System

Information Management System Information Management System Pertemuan II Magister Teknik Elektro Universitas Udayana 1/ 40 Organizations, Managers, & Information To understand how information flows in an organization, we need to understand

More information

Chapter 13: Program Development and Programming Languages

Chapter 13: Program Development and Programming Languages 15 th Edition Understanding Computers Today and Tomorrow Comprehensive Chapter 13: Program Development and Programming Languages Deborah Morley Charles S. Parker Copyright 2015 Cengage Learning Learning

More information

Chapter 13: Program Development and Programming Languages

Chapter 13: Program Development and Programming Languages Understanding Computers Today and Tomorrow 12 th Edition Chapter 13: Program Development and Programming Languages Learning Objectives Understand the differences between structured programming, object-oriented

More information

Assuming the Role of Systems Analyst & Analysis Alternatives

Assuming the Role of Systems Analyst & Analysis Alternatives Assuming the Role of Systems Analyst & Analysis Alternatives Nature of Analysis Systems analysis and design is a systematic approach to identifying problems, opportunities, and objectives; analyzing the

More information

IT2404 Systems Analysis and Design (Compulsory)

IT2404 Systems Analysis and Design (Compulsory) Systems Analysis and Design (Compulsory) BIT 1 st YEAR SEMESTER 2 INTRODUCTION This is one of the 4 courses designed for Semester 1 of Bachelor of Information Technology Degree program. CREDITS: 04 LEARNING

More information

Chapter 3 Managing the Information Systems (IS) Project

Chapter 3 Managing the Information Systems (IS) Project Content Chapter 3 Managing the Information Systems (IS) Project Process of managing IS projects Skills required to be an effective project manager Skills and activities of a project manager during project

More information

CSC 342 Semester I: 1425-1426H (2004-2005 G)

CSC 342 Semester I: 1425-1426H (2004-2005 G) CSC 342 Semester I: 1425-1426H (2004-2005 G) Software Engineering Systems Analysis: Requirements Structuring Context & DFDs. Instructor: Dr. Ghazy Assassa Software Engineering CSC 342/Dr. Ghazy Assassa

More information

Object-Oriented Analysis. with the Unified Process. John W. Satzinger Southwest Missouri State University. Robert B. Jackson Brigham Young University

Object-Oriented Analysis. with the Unified Process. John W. Satzinger Southwest Missouri State University. Robert B. Jackson Brigham Young University Object-Oriented Analysis and Design with the Unified Process John W. Satzinger Southwest Missouri State University Robert B. Jackson Brigham Young University Stephen D. Burd University of New Mexico ALL

More information

1 INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN

1 INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN 1 INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN 1.1 INTRODUCTION Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. In this dynamic

More information

Process/Workflow Analysis Quiz

Process/Workflow Analysis Quiz Process/Workflow Analysis Quiz Question ID: 1 Outline Section: WF A flowchart can be used to show all except A: the specifications of the system. B: re-engineered clarity. C: existing confusion. D: the

More information

SYSTEMS ANALYSIS AND DESIGN DO NOT COPY

SYSTEMS ANALYSIS AND DESIGN DO NOT COPY Systems Analysis and Design in a Changing World, Fourth Edition -488-6-5 Copyright 7 Thomson Course Technology. All rights reserved. FOURTH EDITION SYSTEMS ANALYSIS AND DESIGN IN A C HANGING W ORLD John

More information

MAHATMA GANDHI UNIVERSITY SCHOOL OF DISTANCE EDUCATION (MGU CBCSS UG SDE 2012)

MAHATMA GANDHI UNIVERSITY SCHOOL OF DISTANCE EDUCATION (MGU CBCSS UG SDE 2012) MAHATMA GANDHI UNIVERSITY SCHOOL OF DISTANCE EDUCATION (MGU CBCSS UG SDE 2012) B.Sc Computer Science Semester V BCS 502 Core-19: System Analysis &Design Multiple Choice questions 1... includes review of

More information

Foundations for Systems Development

Foundations for Systems Development Foundations for Systems Development ASSIGNMENT 1 Read this assignment introduction. Then, read Chapter 1, The Systems Development Environment, on pages 2 25 in your textbook. What Is Systems Analysis and

More information

(Refer Slide Time 00:56)

(Refer Slide Time 00:56) Software Engineering Prof.N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-12 Data Modelling- ER diagrams, Mapping to relational model (Part -II) We will continue

More information

Chapter 7: Structuring System Process Requirements

Chapter 7: Structuring System Process Requirements Chapter 7: Structuring System Process Requirements Multiple Choice Questions 1. Data flow diagrams that concentrate on the movement of data between processes are referred to as: a. process models b. data

More information

LECTURE 1. SYSTEMS DEVELOPMENT

LECTURE 1. SYSTEMS DEVELOPMENT LECTURE 1. SYSTEMS DEVELOPMENT 1.1 INFORMATION SYSTEMS System A system is an interrelated set of business procedures used within one business unit working together for a purpose A system has nine characteristics

More information

1. Process Modeling. Process Modeling (Cont.) Content. Chapter 7 Structuring System Process Requirements

1. Process Modeling. Process Modeling (Cont.) Content. Chapter 7 Structuring System Process Requirements Content Chapter 7 Structuring System Process Requirements Understand the logical (&physical) process modeling by using data flow diagrams (DFDs) Draw DFDs & Leveling Balance higher-level and lower-level

More information

Java Application Developer Certificate Program Competencies

Java Application Developer Certificate Program Competencies Java Application Developer Certificate Program Competencies After completing the following units, you will be able to: Basic Programming Logic Explain the steps involved in the program development cycle

More information

Chapter 10 Practical Database Design Methodology and Use of UML Diagrams

Chapter 10 Practical Database Design Methodology and Use of UML Diagrams Chapter 10 Practical Database Design Methodology and Use of UML Diagrams Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 10 Outline The Role of Information Systems in

More information

The Project Planning Process Group

The Project Planning Process Group 3 The Project Planning Process Group............................................... Terms you ll need to understand: Activity Activity attributes Activity list Activity on arrow diagram (AOA) Activity

More information

ATM Case Study Part 1

ATM Case Study Part 1 ATM Case Study Part 1 A requirements document specifies the purpose of the ATM system and what it must do. Requirements Document A local bank intends to install a new automated teller machine (ATM) to

More information

Flowcharting, pseudocoding, and process design

Flowcharting, pseudocoding, and process design Systems Analysis Pseudocoding & Flowcharting 1 Flowcharting, pseudocoding, and process design The purpose of flowcharts is to represent graphically the logical decisions and progression of steps in the

More information

Chapter 10 Practical Database Design Methodology and Use of UML Diagrams

Chapter 10 Practical Database Design Methodology and Use of UML Diagrams Chapter 10 Practical Database Design Methodology and Use of UML Diagrams Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 10 Outline The Role of Information Systems in

More information

Use project management tools

Use project management tools Use project management tools Overview Using project management tools play a large role in all phases of a project - in planning, implementation, and evaluation. This resource will give you a basic understanding

More information

Top Application Development Terms Fifteen essential definitions you need to know

Top Application Development Terms Fifteen essential definitions you need to know Top Fifteen essential definitions you need to know Fifteen Essential We know it s not always easy to keep up-to-date with the latest application development terms. That s why we have put together the top

More information

Information Technology (IT) Introduction to System Analysis and Design. Information System. Information System Components

Information Technology (IT) Introduction to System Analysis and Design. Information System. Information System Components Information Technology (IT) Introduction to System Analysis and Design Peter Lo A combination of Hardware Software Telecommunications systems Support business operations Improve productivity Help managers

More information

Systems Investigation and Analysis. Systems Development. What is it? Why Plan?

Systems Investigation and Analysis. Systems Development. What is it? Why Plan? C H A P T E R 12 Systems Investigation and Analysis Systems Development What is it? If you can t do it better, why do it? -Herbert H. Dow, Founder, Dow Chemical Company Why Plan? Why do we need a process?

More information

RE: It's all about the ERP Edward Jackson Email this Author 2/8/2014 1:34:02 PM

RE: It's all about the ERP Edward Jackson Email this Author 2/8/2014 1:34:02 PM Discussion Discussion Topic 1 What is Enterprise Resource Planning (ERP) and what is its purpose? What problems do analysts often encounter when they try to implement an ERP package. RE: It's all about

More information

Project Time Management

Project Time Management Project Time Management Plan Schedule Management is the process of establishing the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule.

More information

How To Develop Software

How To Develop Software Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which

More information

HOW TO START WORKING WITH P2WARE PROJECT MANAGER 7?

HOW TO START WORKING WITH P2WARE PROJECT MANAGER 7? HOW TO START WORKING WITH P2WARE PROJECT MANAGER 7? This document contains introduction to P2ware Project Manager 7 views (P2ware Project Manager 7 walkthrough) and shows how to create high quality plans

More information

Programming and Software Development CTAG Alignments

Programming and Software Development CTAG Alignments Programming and Software Development CTAG Alignments This document contains information about four Career-Technical Articulation Numbers (CTANs) for Programming and Software Development Career-Technical

More information

Why Data Flow Diagrams?

Why Data Flow Diagrams? Flow Diagrams A structured analysis technique that employs a set of visual representations of the data that moves through the organization, the paths through which the data moves, and the processes that

More information

Chapter 1 The Systems Development Environment

Chapter 1 The Systems Development Environment Your Objects of SA&D Study Chapter 1 The Systems Development Environment 2011 by Prentice Hall: J.A.Hoffer et.al., Modern Systems Analysis & Design, 6 th Edition 1/55 2/55 Course Content Fundamental of

More information

Online Chapter A The Role of the Systems Analyst

Online Chapter A The Role of the Systems Analyst Systems Analysis and Design in a Changing World, sixth edition A-1 Online Chapter A The Role of the Systems Analyst Table of Contents Chapter Overview Learning Objectives Why read this chapter? This chapter

More information

Student Attendance Through Mobile Devices

Student Attendance Through Mobile Devices Student Attendance Through Mobile Devices Anurag Rastogi Kirti Gupta Department of Computer Science and Engineering National Institute of Technology Rourkela Rourkela-769 008, Odisha, India Student Attendance

More information

A Project Based Approach for Teaching System Analysis, Design, and Implementation Courses

A Project Based Approach for Teaching System Analysis, Design, and Implementation Courses A Project Based Approach for Teaching System Analysis, Design, and Implementation Courses Nabil A. Yousif 1 and Masoud Naghedolfeizi 2 Abstract-In curricula of Computer Information Systems at Fort Valley

More information

Applying Agile Methods in Rapidly Changing Environments

Applying Agile Methods in Rapidly Changing Environments Applying Agile Methods in Changing Environments 7/23/2002 1 Applying Agile Methods in Rapidly Changing Environments Peter Kutschera IBM Unternehmensberatung GmbH Am Fichtenberg 1, D-71803 Herrenberg Steffen

More information

PROJECT TIME MANAGEMENT

PROJECT TIME MANAGEMENT 6 PROJECT TIME MANAGEMENT Project Time Management includes the processes required to ensure timely completion of the project. Figure 6 1 provides an overview of the following major processes: 6.1 Activity

More information

MULTIPLE CHOICE. Choose the one alternative that best completes the statement or answers the question.

MULTIPLE CHOICE. Choose the one alternative that best completes the statement or answers the question. Exam Name MULTIPLE CHOICE. Choose the one alternative that best completes the statement or answers the question. 1) Which of the following requires a systems development method that uses a data orientation

More information

Software Development. Topic 1 The Software Development Process

Software Development. Topic 1 The Software Development Process Software Development Topic 1 The Software Development Process 1 The Software Development Process Analysis Design Implementation Testing Documentation Evaluation Maintenance 2 Analysis Stage An Iterative

More information

MCQ on Management Information System. Answer Key

MCQ on Management Information System. Answer Key MCQ on Management Information System. Answer Key 1.Management information systems (MIS) 1. create and share documents that support day-today office activities 2. process business transactions (e.g., time

More information

Object Oriented Programming. Risk Management

Object Oriented Programming. Risk Management Section V: Object Oriented Programming Risk Management In theory, there is no difference between theory and practice. But, in practice, there is. - Jan van de Snepscheut 427 Chapter 21: Unified Modeling

More information

GCE APPLIED ICT A2 COURSEWORK TIPS

GCE APPLIED ICT A2 COURSEWORK TIPS GCE APPLIED ICT A2 COURSEWORK TIPS COURSEWORK TIPS A2 GCE APPLIED ICT If you are studying for the six-unit GCE Single Award or the twelve-unit Double Award, then you may study some of the following coursework

More information

Critical Path Analysis & PERT Charts (taken from www.business.com.

Critical Path Analysis & PERT Charts (taken from www.business.com. Critical Path Analysis & PERT Charts (taken from www.business.com. - Planning and scheduling more complex projects Critical Path Analysis and PERT are powerful tools that help you to schedule and manage

More information

Project Scheduling & Tracking

Project Scheduling & Tracking Project Scheduling & Tracking Traditional Techniques: Work Breakdown Structure (WBS) Gantt Charts Precedence Diagrams Earned Value Planning It is the mark of an instructed mind to rest satisfied with the

More information

A. Waterfall Model - Requirement Analysis. System & Software Design. Implementation & Unit Testing. Integration & System Testing.

A. Waterfall Model - Requirement Analysis. System & Software Design. Implementation & Unit Testing. Integration & System Testing. Processing Models Of SDLC Mrs. Nalkar Sanjivani Baban Asst. Professor, IT/CS Dept, JVM s Mehta College,Sector 19, Airoli, Navi Mumbai-400708 Nalkar_sanjivani@yahoo.co.in Abstract This paper presents an

More information

General Problem Solving Model. Software Development Methodology. Chapter 2A

General Problem Solving Model. Software Development Methodology. Chapter 2A General Problem Solving Model Software Development Methodology These focus on understanding what the problem is about Chapter 2A Concerned with understanding more about the nature of the problem and possible

More information

A system is a set of integrated components interacting with each other to serve a common purpose.

A system is a set of integrated components interacting with each other to serve a common purpose. SYSTEM DEVELOPMENT AND THE WATERFALL MODEL What is a System? (Ch. 18) A system is a set of integrated components interacting with each other to serve a common purpose. A computer-based system is a system

More information

TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW

TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Year 2014, Vol. 1, issue 1, pp. 49-56 Available online at: http://journal.iecuniversity.com TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Singh RANDEEP a*, Rathee AMIT b a* Department of

More information

Systems Analysis and Design

Systems Analysis and Design Systems Analysis and Design Slides adapted from Jeffrey A. Hoffer, University of Dayton Joey F. George, Florida State University Joseph S. Valacich, Washington State University Modern Systems Analysis

More information

Software Engineering Question Bank

Software Engineering Question Bank Software Engineering Question Bank 1) What is Software Development Life Cycle? (SDLC) System Development Life Cycle (SDLC) is the overall process of developing information systems through a multi-step

More information

10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design

10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design Session # 3 Contents Systems Analysis and Design 2 1 Tiers of Software Development 10/4/2013 Information system development project Realistic behavior 3 Information system development project System Development

More information

The Software Development Life Cycle (SDLC)

The Software Development Life Cycle (SDLC) Document ID: Version: 2.0 1 / 22 2 TABLE OF CONTENTS INTRODUCTION... 4 THE SDLC WATERFALL... 4 ALLOWED VARIATIONS... 5 OTHER SDLC MODELS... 6 REFERENCES... 7 GENERIC STAGE... 8 KICKOFF PROCESS... 8 INFORMAL

More information

5/19/2014. 1 Professor Lili Saghafi

5/19/2014. 1 Professor Lili Saghafi 5/19/2014 1 Professor Lili Saghafi MANAGING INFORMATION TECHNOLOGY Lecture 9 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT By : Prof. Lili Saghafi 1-2 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT Large

More information

1. Global E Business and Collaboration. Lecture 2 TIM 50 Autumn 2012

1. Global E Business and Collaboration. Lecture 2 TIM 50 Autumn 2012 1. Global E Business and Collaboration Lecture 2 TIM 50 Autumn 2012 Objective of the Learning The Major Feature of Business Systems Performance of Business Organization Levels of Business management The

More information

Algorithms, Flowcharts & Program Design. ComPro

Algorithms, Flowcharts & Program Design. ComPro Algorithms, Flowcharts & Program Design ComPro Definition Algorithm: o sequence of steps to be performed in order to solve a problem by the computer. Flowchart: o graphical or symbolic representation of

More information

Answers to Review Questions

Answers to Review Questions Tutorial 2 The Database Design Life Cycle Reference: MONASH UNIVERSITY AUSTRALIA Faculty of Information Technology FIT1004 Database Rob, P. & Coronel, C. Database Systems: Design, Implementation & Management,

More information

Brief Contents. Part Three: Decisions and Strategies. Part One: Information Technology Infrastructure. Part Four: Organizing Businesses and Systems

Brief Contents. Part Three: Decisions and Strategies. Part One: Information Technology Infrastructure. Part Four: Organizing Businesses and Systems Brief Contents 1 Introduction Part One: Information Technology Infrastructure 2 Information Technology Foundations 3 Networks and Telecommunications 4 Database Management Part Two: Business Integration

More information

JOURNAL OF OBJECT TECHNOLOGY

JOURNAL OF OBJECT TECHNOLOGY JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5. No. 8, November-December 2006 Requirements Engineering Tasks Donald Firesmith,

More information

NASCIO EA Development Tool-Kit Solution Architecture. Version 3.0

NASCIO EA Development Tool-Kit Solution Architecture. Version 3.0 NASCIO EA Development Tool-Kit Solution Architecture Version 3.0 October 2004 TABLE OF CONTENTS SOLUTION ARCHITECTURE...1 Introduction...1 Benefits...3 Link to Implementation Planning...4 Definitions...5

More information

Chapter 12 Programming Concepts and Languages

Chapter 12 Programming Concepts and Languages Chapter 12 Programming Concepts and Languages Chapter 12 Programming Concepts and Languages Paradigm Publishing, Inc. 12-1 Presentation Overview Programming Concepts Problem-Solving Techniques The Evolution

More information

Determining requirements

Determining requirements Systems Analysis Determining requirements ผ สอน ดร.สล ล บ ญพราหมณ ITM-631 Information System Development ... การจะพ ฒนาท กส งท กอย างให เจร ญน น จะต องสร างและเสร ม ข นจากพ นฐานเด มท ม อย ก อนท งส น ถ

More information

The ROI of Test Automation

The ROI of Test Automation The ROI of Test Automation by Michael Kelly www.michaeldkelly.com Introduction With the exception of my first project team out of college, in every project team since, I ve had to explain either what automated

More information

Understanding Data Flow Diagrams Donald S. Le Vie, Jr.

Understanding Data Flow Diagrams Donald S. Le Vie, Jr. Understanding Flow Diagrams Donald S. Le Vie, Jr. flow diagrams (DFDs) reveal relationships among and between the various components in a program or system. DFDs are an important technique for modeling

More information

Table of Contents Author s Preface... 3 Table of Contents... 5 Introduction... 6 Step 1: Define Activities... 7 Identify deliverables and decompose

Table of Contents Author s Preface... 3 Table of Contents... 5 Introduction... 6 Step 1: Define Activities... 7 Identify deliverables and decompose 1 2 Author s Preface The Medialogist s Guide to Project Time Management is developed in compliance with the 9 th semester Medialogy report The Medialogist s Guide to Project Time Management Introducing

More information

SYSTEMS ANALYSIS DESIGN

SYSTEMS ANALYSIS DESIGN SYSTEMS ANALYSIS DESIGN Third Edition ALAN DENNIS Indiana University BARBARA HALEY WIXOM University of Virginia ROBERTA M. ROTH University of Northern Iowa WILEY John Wiley & Sons, Inc. http://www.wiley.com/college/dennis

More information

Unit Title: Personnel Information Systems Unit Reference Number: F/601/7510 Guided Learning Hours: 160 Level: Level 5 Number of Credits: 18

Unit Title: Personnel Information Systems Unit Reference Number: F/601/7510 Guided Learning Hours: 160 Level: Level 5 Number of Credits: 18 Unit Title: Personnel Information Systems Unit Reference Number: F/601/7510 Guided Learning Hours: 160 Level: Level 5 Number of Credits: 18 Unit objective and aim(s): This unit aims to give learners a

More information

Cambridge International AS and A Level Computer Science

Cambridge International AS and A Level Computer Science Topic support guide Cambridge International AS and A Level Computer Science 9608 For examination from 2017 Topic 4.4.3 Project management PERT and GANTT charts Cambridge International Examinations retains

More information

CIS Project Management

CIS Project Management Topic # 4 CIS Project Management A Correspondence of Positions and Languages/Communications in CIS Analysis, Design, Development and Implementation (Engineering) Industry Correspondence of Positions and

More information

SWEN 256 Software Process & Project Management

SWEN 256 Software Process & Project Management SWEN 256 Software Process & Project Management Plan: Identify activities. No specific start and end dates. Estimating: Determining the size & duration of activities. Schedule: Adds specific start and end

More information

Requirements Management

Requirements Management REQUIREMENTS By Harold Halbleib Requirements Management Identify, Specify, Track and Control Requirements Using a Standard Process About the author... Harold Halbleib has a degree in Electrical Engineering

More information

Intellect Platform - The Workflow Engine Basic HelpDesk Troubleticket System - A102

Intellect Platform - The Workflow Engine Basic HelpDesk Troubleticket System - A102 Intellect Platform - The Workflow Engine Basic HelpDesk Troubleticket System - A102 Interneer, Inc. Updated on 2/22/2012 Created by Erika Keresztyen Fahey 2 Workflow - A102 - Basic HelpDesk Ticketing System

More information

How To Understand Information Systems

How To Understand Information Systems Management Information Systems Information Systems: Concepts and Management Dr. Shankar Sundaresan (Adapted from Introduction to IS, Rainer and Turban) CHAPTER OUTLINE Types of Information Systems Why

More information

AN OVERVIEW OF SYSTEMS ANALYSIS: SYSTEMS ANALYSIS AND THE ROLE OF THE SYSTEMS ANALYST. Lecture 1. 21.10.2014, Tuesday

AN OVERVIEW OF SYSTEMS ANALYSIS: SYSTEMS ANALYSIS AND THE ROLE OF THE SYSTEMS ANALYST. Lecture 1. 21.10.2014, Tuesday AN OVERVIEW OF SYSTEMS ANALYSIS: SYSTEMS ANALYSIS AND THE ROLE OF THE SYSTEMS ANALYST Lecture 1 21.10.2014, Tuesday 2 A Series of Lectures 1.The Role of the Systems 2.Project Planning and Project Management

More information

Moving from CS 61A Scheme to CS 61B Java

Moving from CS 61A Scheme to CS 61B Java Moving from CS 61A Scheme to CS 61B Java Introduction Java is an object-oriented language. This document describes some of the differences between object-oriented programming in Scheme (which we hope you

More information

Peter Mileff PhD SOFTWARE ENGINEERING. The Basics of Software Engineering. University of Miskolc Department of Information Technology

Peter Mileff PhD SOFTWARE ENGINEERING. The Basics of Software Engineering. University of Miskolc Department of Information Technology Peter Mileff PhD SOFTWARE ENGINEERING The Basics of Software Engineering University of Miskolc Department of Information Technology Introduction Péter Mileff - Department of Information Engineering Room

More information

Total Quality Management (TQM) Quality, Success and Failure. Total Quality Management (TQM) vs. Process Reengineering (BPR)

Total Quality Management (TQM) Quality, Success and Failure. Total Quality Management (TQM) vs. Process Reengineering (BPR) Total Quality Management (TQM) Quality, Success and Failure Total Quality Management (TQM) is a concept that makes quality control a responsibility to be shared by all people in an organization. M7011

More information

pm4dev, 2015 management for development series Project Schedule Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS

pm4dev, 2015 management for development series Project Schedule Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS pm4dev, 2015 management for development series Project Schedule Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS A methodology to manage development

More information

Digital Industries Trailblazer Apprenticeship. Software Developer - Occupational Brief

Digital Industries Trailblazer Apprenticeship. Software Developer - Occupational Brief Digital Industries Trailblazer Apprenticeship Software Developer - Occupational Brief Table of Contents Contents 1 Software Developer Trailblazer Apprenticeship Introduction... 1 2 Software Developer Trailblazer

More information

Basic Trends of Modern Software Development

Basic Trends of Modern Software Development DITF LDI Lietišķo datorsistēmu programmatūras profesora grupa e-business Solutions Basic Trends of Modern Software Development 2 3 Software Engineering FAQ What is software engineering? An engineering

More information

Sistemi ICT per il Business Networking

Sistemi ICT per il Business Networking Corso di Laurea Specialistica Ingegneria Gestionale Sistemi ICT per il Business Networking Software Development Processes Docente: Vito Morreale (vito.morreale@eng.it) 17 October 2006 1 The essence of

More information

Meta-Model specification V2 D602.012

Meta-Model specification V2 D602.012 PROPRIETARY RIGHTS STATEMENT THIS DOCUMENT CONTAINS INFORMATION, WHICH IS PROPRIETARY TO THE CRYSTAL CONSORTIUM. NEITHER THIS DOCUMENT NOR THE INFORMATION CONTAINED HEREIN SHALL BE USED, DUPLICATED OR

More information

Managing Successful Software Development Projects Mike Thibado 12/28/05

Managing Successful Software Development Projects Mike Thibado 12/28/05 Managing Successful Software Development Projects Mike Thibado 12/28/05 Copyright 2006, Ambient Consulting Table of Contents EXECUTIVE OVERVIEW...3 STATEMENT OF WORK DOCUMENT...4 REQUIREMENTS CHANGE PROCEDURE...5

More information

Why Documentation Is Important. Documentation of Systems. Document Flowcharts. Types of Documentation

Why Documentation Is Important. Documentation of Systems. Document Flowcharts. Types of Documentation Core Concepts of ACCOUNTING INFORMATION SYSTEMS Moscove, Simkin & Bagranoff Chapter 2 Documenting Accounting Information Systems Developed by: S. Bhattacharya, Ph.D. Florida Atlantic University Introduction

More information

Topic # 08. Structuring System Process Requirements. CIS Life Cycle and Requirements Structuring Stage

Topic # 08. Structuring System Process Requirements. CIS Life Cycle and Requirements Structuring Stage Topic # 08 Structuring System Process Requirements CIS Life Cycle and Requirements Structuring Stage Objectives 1. Data Flow Diagrams 2. Rules and Guidelines to DFD development that lead to accurate and

More information

Fundamentals of Java Programming

Fundamentals of Java Programming Fundamentals of Java Programming This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and exclusive use by instructors

More information

Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality

Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality Current Research Team: Prof. Victor R. Basili Forrest Shull, Ph.D. Guilherme H. Travassos, D.Sc. (1)

More information