ECE480 Notes - June 23 rd 2008 LESSON 1 : Overview of...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: June 23 rd 2008 LESSON 1 : Overview of Objects Object Oriented Design 1. Encapsulation: Using private data a. (i.e. information is Private, protected, doesn’t change) 2. Inheritance: Base (origination/parent) & Derive (children) a. Inherit properties from parents and also contains more properties b. (ie. constructor) c. Foundation and base of writing UML i. Bring down classes, set public and private, drag drop code, and regenerate on your choosing 3. Polymorphism: Greek definition is many forms/many changes a. (ie. overloading function, template, such as overwriting data types) b. Pure virtual function: Abstract function (ie. virtual function = 0) Example class class_name public: methods (operations , functions) member functions private: data members, attributes UML : Uses the terms operations, attributes Rational Rose Together Soft C++, Visual, C# June 24 th 2008 LESSON 2 : Environmental Model Select Project Name How do we start a project? - System (draw a cloud, system includes a cloud)- System can have multiple actors/events- Actor (person/object) -> Event (person/object activating robot) -> Cloud (robot) o Actors Initiating: someone who creates an event, draws an arrow to cloud (left Participating: someone who’s in background, no arrow to cloud (right o Event Actors cause an event to occur Events can be internal (within a cloud) o Cloud In essence, the project LESSON 3 : System Development Life Cycle SDLC: System Development Life Cycle- Systems can be software or hardware- Parts of a System: contains multiple components o Model Prototypes Diagrams Supporting Documents o Subsystem Hardware Software Processes (Life Cycle: Birth to Maturity) NOTE:These 5 steps incorporate the topics for the next 5 weeks Testing is embedded in every process stage 1. Planning (Requirements) a. Narrative Description: describe what your system will do (one paragraph) b. Feasibility: constraints/limitations i. Budget limitations ii. Time limitations c. Steps d. System Functions: ie. System does something, verb words e. System Attributes: Can be a function, but with properties ie. Recording in 15 min f. Environmental Diagram g. Prototype h. Resource Allocation Management 2. Analysis a. Process of determining detailed requirements in the form of a model (UML) b. System Analyst: Someone who looks at the planning c. Diagrams i. Conceptual Diagram: Graphical representation of system, shows objects and relationship (multiple) ii. Sequence Diagram: Graphical representation of system, shows dynamics of system (multiple) d. Contract i. Pre-Conditions: Way it exists now (before) ii. Post-Conditions: Results or changes (after) iii. State Diagram 3. Design a. Drawing blueprints of a system, schematic, diagrams b. Diagrams i. Use Case (Interaction) Diagram: Representation of dynamics in system ii. Class Diagram: Representation of statics in system 4. Implementation (Construction) a. Programmers b. Computer Engineers c. Construction d. Integration...
View Full Document

This note was uploaded on 10/24/2010 for the course ECE 480 taught by Professor Monemi during the Spring '10 term at Cal Poly Pomona.

Page1 / 40

ECE480 Notes - June 23 rd 2008 LESSON 1 : Overview of...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online