CPSC 371 John D. McGregor Session 1 Introduction.

13
CPSC 371 John D. McGregor Session 1 Introduction

Transcript of CPSC 371 John D. McGregor Session 1 Introduction.

Page 1: CPSC 371 John D. McGregor Session 1 Introduction.

CPSC 371

John D. McGregorSession 1

Introduction

Page 2: CPSC 371 John D. McGregor Session 1 Introduction.

Course Checklist

• Read the syllabus• Visit my website

www.cs.clemson.edu/~johnmc and the course’s site under that

• Load software – more shortly• Read: http://www.computer.org/portal/web/swebok/html/ch1#Ref1

Page 3: CPSC 371 John D. McGregor Session 1 Introduction.

Systems Approach

• Read chapters 1 – 4 in http://www.incose.org/productspubs/doc/systemsapproach.pdf• Read sections “What is a system” and

“systems thinking” http://www.sebokwiki.org/wiki/INCOSE_Systems_Engineering_Handbook

• Explore the first parts of http://thinksysml.org

Page 4: CPSC 371 John D. McGregor Session 1 Introduction.

Running example - 1

• A system consists of a dongle that attaches to the OBD port of a vehicle.

• The dongle is attached to a cell phone.• The cell phone establishes a connection with

the user’s personal cloud and uploads performance data from the car.

• This data is available to the vehicle manufacturer and the user’s insurance company.

Page 5: CPSC 371 John D. McGregor Session 1 Introduction.

Running example - 2

• This example will be the basis for projects this semester.

Page 6: CPSC 371 John D. McGregor Session 1 Introduction.

Class on August 26th

• Jasprit Gill will talk about aspects of the running problem we will use this semester.

Page 7: CPSC 371 John D. McGregor Session 1 Introduction.

Class on August 28th

• Yates Monteith will show you how to download Polarsys 0.8 and create use cases.

• He will also show you how to use EPF for process documentation.

• After this class you will be able to install the third party pieces defined at http://thinksysml.org/ThirdParty.html

Page 8: CPSC 371 John D. McGregor Session 1 Introduction.

Systems analysis

• Lots of different definitions and directions• Defining data layouts• Designing data base records• The examination of a problem and the

creation of its solution. Systems analysis is effective when all sides of the problem are reviewed. Systems design is most effective when more than one solution can be proposed.

Page 9: CPSC 371 John D. McGregor Session 1 Introduction.

Systems Engineering

• I’m going to use a definition from INCOSE that is found in http://www.pedalion.com.au/files/sehandbookv3.pdf

• Systems engineering is a discipline that concentrates on the design and application of the whole (system) as distinct from the parts. It involves looking at a problem in its entirety, taking into account all the facets and all the variables and relating the social to the technical aspect.

Page 10: CPSC 371 John D. McGregor Session 1 Introduction.

Systems Thinking

• Rather than decomposing things into smaller pieces systems thinking looks at bigger and bigger pictures

Page 11: CPSC 371 John D. McGregor Session 1 Introduction.

Example

• Use handout• See http://

www.albany.edu/acc/courses/fall97/acc681/ch7.html for the full text

Page 12: CPSC 371 John D. McGregor Session 1 Introduction.

Sept 2nd

• I’ll be back• Each team will do a no more than 10 minute

presentation on your area• That implies we have teams – 3 teams of 4 but

one team has an extra person• Give me your team line up before you leave

today• Each team will be given one part of the

problem: OBD, smart phone, cloud