Software Development for Business Applications in a Nutshell by Tugrul Esendal De Montfort University for 2 nd and final year project students.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

Revision from last week  Assumptions are potential failure points in a project. They need to be monitored and managed. At the start of the project they.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
CATEGORIES OF INFORMATION There are three main categories of business information,and these are related to the purpose for which the information is utilized.
System Design and Analysis
CIS101 Introduction to Computing Week 06. Agenda Your questions Resume project HTML Project Two This week online Next class.
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Harris JTRS Project The A-Team Garrett Wampole Ben Litchfield Jason Offord Jason Gillman David Bryant.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
1004INT Information Systems Week 11 Databases as Business Tools.
WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code.
1 Software Engineering--Introduction. 2 1.Syllabus, grading, schedule--class + lab--will all be on 2.Contact.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
CIS101 Introduction to Computing Week 06. Agenda Your questions Resume project HTML Project Two This week online Next class.
CSSE 375 Software Construction and Evolution: Configuration Management
IBE312: Ch15 Building an IA Team & Ch16 Tools & Software 2013.
1 L07SoftwareDevelopmentMethod.pptCMSC 104, Version 8/06 Software Development Method Topics l Software Development Life Cycle Reading l Section 1.4 – 1.5.
Introduction to Systems Analysis and Design Trisha Cummings.
CryptKeeper Project Plan 1 CryptKeeper Project Plan.
Chapter 9 Moving to Design. The Structured Approach To Designing The Application Architecture Module-an identifiable component of a computer program that.
CS 0004 –Lecture 8 Jan 24, 2011 Roxana Gheorghiu.
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Introduction to SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2009.
Systems Life Cycle DESIGN STAGE
Chapter 14 Information System Development
OHT 11.1 © Marketing Insights Limited 2004 Chapter 9 Analysis and Design EC Security.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Senior Project Computation Linguistics Research System Senior Project Computation Linguistics Research System Supervisor Dr. Imad AL-Sughaiyer Submitted.
1 3. Computing System Fundamentals 3.1 Language Translators.
The Nature of Data & Information. Data is the raw material entered into an information system. It is the input of the system. Data can be thought of as.
Software Testing. What is Testing? The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation.
Systems Analysis and Design in a Changing World, Fourth Edition
K. Ingram (with thanks to A. Seddon) Staffordshire UNIVERSITY School of Computing Introduction to Software System Design.
CASE Tools Union Palenshus. In the early days… ► Software engineering tools consisted solely of translators, compilers, assemblers, linkers, loaders,
PICTURE your design. Purpose : Functions & Content Functions the facilities that make the content of the ICT useful for relevant users and other ICT’s.
Interfaces. Joseph Sant Sheridan College.. Objectives Discuss reasoning behind interfaces using a scenario. Interfaces and Contracts. Syntax examples.
Week 14 Introduction to Computer Science and Object-Oriented Programming COMP 111 George Basham.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Write a function rule for a graph EXAMPLE 3 Write a rule for the function represented by the graph. Identify the domain and the range of the function.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Project Deliverables CIS 4328 – Senior Project 2 And CEN Engineering of Software 2.
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
CS 5150 Software Engineering Lecture 9 Requirements 3.
Software Engineering Session 12 INFM 603. Software Software represents an aspect of reality –Input and output represent the state of the world –Software.
Appendix 2 Automated Tools for Systems Development
Software Project Configuration Management
Jim Fawcett CSE681 – Software Modeling and Analysis Fall 2017
Using Excel to Construct Basic Tools for Understanding Variation
Software Specification Tools
Unified Modeling Language
System Design.
Software Maintenance.
Systems Analysis and Design
Chapter 11 Information System Development
School of EE and Computer Science
Software Life Cycle Risk Management
Formulation of Abstract Machine for SPM Based on Finite State Machine
Introduction to Systems Analysis and Design
Presenting: Aimee & Catherine.
X-DIS/XBRL Phase 2 Kick-Off
Georg Umgiesser and Natalja Čerkasova
Members: Keshava Shiva Sanjeeve Kareena
G061 - Data Dictionary.
Software Re-engineering and Reverse Engineering
Presentation transcript:

Software Development for Business Applications in a Nutshell by Tugrul Esendal De Montfort University for 2 nd and final year project students

Are you starting a software development project, where the end-product is a business application? Then, you may find the following useful …

 Problem Domain Describe what the product is going to do, and the business environment in which it going to run, in your own words, using non-technical terms A picture is worth how many words? A rich picture is a good tool to use for this purpose. The final version of your rich picture should give you a firm basis on which to carry out problem analysis

 Tasks Identify the tasks you need to carry out to develop the product For software development projects, the tasks are activities like:  Problem Analysis (using the rich picture)  Identification of actors  Functionality requirements  Design  Implementation  Documentation  Product demonstration

 Deadlines Identify all deadlines (interim and/or final) you need to meet

 Draw a Gannt Chart of tasks to perform against time, highlighting all deadlines. Use “weeks” as unit of time.  Do a risk analysis Threat to successful completionMeasures against threat Poor time management? Unfamiliar technology? Unexpected loss of code/data/doc? What else do you this is a treat??

CompetitorStrengthsWeaknessesComments It is important to know what competitors your product will have How would you use these findings in your own design?

 Identify your actors  For each actor, compile a list of their functionality requirements; use verbs & keywords  For each functionality requirement, compile a list of its data requirements (specifying the name and data type of each data item, like in a data dictionary. You could also identify each data item as being either input or output)

 Identify and name the tables you need  Identify and name the fields in each table  Finalize the data type of each data item  Establish the relationships between tables  Determine what test data you need in the database, to test and demonstrate the product

 Create the database you have designed in your chosen environment, which is SQL-Server, unless specified otherwise  Place in each table the test data you need

 Create the web forms you need to process the data in the chosen environment, which is.NET, unless specified otherwise  Establish the navigational requirements

 Write the code to bring the prototype to life  Test the product  Document the product

And that’s all there is to it