CSE Design Lab – Milestone 11. Introduction1.1 Background and Motivation1.3 Team Members & Task Breakdown1.4 References2. Overall Description2.1 Product Functions and Perspective2.2 User Classes and Perspective2.3 Developing Environment2.4 User Environment2.5 Design/Implementation Constraints2.6 Assumptions and Dependencies3. External Interface Requirements3.1 User Interfaces3.2 Hardware Interfaces3.3 Software Interfaces3.4 Communication Protocols and Interfaces4. System Features4.1 Description and Priority4.2 Action Plan4.3 Functional Requirements5. Other Nonfunctional Requirements5.1 Performance Requirement“Brick’s” hardware5.2 Security Requirements5.3 Software Quality Attributes5.5 User DocumentationCSE Design Lab – Milestone 1Preliminary Specs and Initial Project PlansDavid Festa1. IntroductionMicrosoft Robotics Studio1.1 Background and MotivationRobot control and simulationExtensive toolsetSoftware / hardware combination“interesting”Widely used for education purposes1.3 Team Members & Task BreakdownDavid FestaJames HopkinsDennis O’FlahertyKarl Schwirz1.4 ReferencesMicrosoft Robotics Developer CenterLego Mindstorms NXTMicrosoft Developer Network2. Overall Description2.1 Product Functions and PerspectiveSensors (sound, light, ultrasonic, touch, motors)Expansion, (webcam, lights)Communication link2.2 User Classes and PerspectiveGeneral/academic audience (TBD)2.3 Developing EnvironmentVarious program languagesMicrosoft Visual StudioMicrosoft Visual Simulation2.4 User EnvironmentSimilar to developer (Windows based) (TBD)2.5 Design/Implementation ConstraintsFixed hardware partsBudget (2 robots)Hardware sensors per robot limited2.6 Assumptions and DependenciesAssuming Lego Mindstorms NXT with MS Robotics softwareFurther structure TBD3. External Interface Requirements3.1 User InterfacesComputer, mobile phoneCreate windows based GUI for user to manipulate Possible web based interface3.2 Hardware InterfacesLight, sonar, sensors, touchServo motorsSpeaker output100x64 pixel monochrome LCD displaymicrophone3.3 Software InterfacesWindows basedMatLab, plugins, 3rd party support, LabVIEW3.4 Communication Protocols and InterfacesWeb based/Windows based, Bluetooth, USB4. System Features4.1 Description and Priority4.2 Action PlanSuggested tasks (drive by wire)Adapt and string together series of tasksEnd goal not determined on purpose (creativity)4.3 Functional RequirementsWindows computer, Lego Mindstorms hardware5. Other Nonfunctional Requirements5.1 Performance RequirementFor robot’s software…“Brick’s” hardware* 32-bit ARM7 microprocessor* 256 Kbytes FLASH, 64 Kbytes RAM* 8-bit microprocessor* 4 Kbytes FLASH, 512 Byte RAM* Bluetooth wireless communication* USB 2.0 port * 4 input ports, 6 wire digital platform* 3 output ports, 6 wire digital platform* Dot matrix display 60 x 100 pixels* Loudspeaker 8 KHz sound quality* Power, 6 AA Batteries5.2 Security RequirementsClosed system for nowWeb based security TBD (Bluetooth hijacking)5.3 Software Quality AttributesUser friendly (hobbyist in mind)ExpandableRobustProven (MySpace, Princeton)5.5 User DocumentationIntuitive GUI allow for ease of
View Full Document