發(fā)布時(shí)間：2021-06-14 01:51

　　與Proteus一樣,MicroCPro在微控制器應(yīng)用的開發(fā)中發(fā)揮了非常重要的作用。然而,它忽略了一個(gè)事實(shí),即大多數(shù)微控制器設(shè)計(jì)人員并不具有很高的編程技能,這就是為什么他們需要程序員的幫助,從而產(chǎn)生依賴性和對(duì)性能的影響。因此,在本研究中,我們解決了這種依賴性,并提出了一個(gè)新的模型,通過該模型,非編程人員/低技能程序員也可以設(shè)計(jì)和編程微控制器應(yīng)用。在我們的新模型中:（1）我們使用拖放技術(shù)幫助用戶設(shè)計(jì)微控制器應(yīng)用,通過界面設(shè)置基本的配置,這是在傳統(tǒng)的工具,即Proteus中還沒有介紹的。（2）這個(gè)工具引入了邏輯塊,用于制作應(yīng)用程序的邏輯流程圖,我們的工具從這些塊生成自動(dòng)的源代碼。（用戶不甚至不需要寫一行代碼）。（3）十六進(jìn)制文件可以通過我們的工具使用從方框圖生成的C代碼生成。（4）最后,用戶可以使用我們的工具在實(shí)際環(huán)境中刻錄微控制器中的十六進(jìn)制文件. 

【文章來源】：西南科技大學(xué)四川省

【文章頁數(shù)】：85 頁

【學(xué)位級(jí)別】：碩士

【文章目錄】：
摘要
ABSTRACT
1 CHAPTER 1-INTRODUCTION
    1.1 Introduction
    1.2 Existing System
    1.3 Discrepancies of existing system
        1.3.1 Nonprofessional user interface
        1.3.2 Limited set of microcontrollers and supporting components
        1.3.3 Provides basic configuration code only
        1.3.4 No interface to provide algorithm of the program
        1.3.5 No actual code generation
        1.3.6 Time consuming procedure
    1.4 Proposed System:
    1.5 Merits of Proposed System
    1.6 Project Scope:
    1.7 Objective of Project
2 CHAPTER 2–REQUIREMENT ANALYSIS
    2.1 Requirement Analysis
    2.2 Functional Requirements:
        2.2.1 User Friendly Interface
        2.2.2 Allow user to drag and drop components
        2.2.3 Allow user to set connection properties
        2.2.4 Taking connection properties as input
        2.2.5 Allow user to make flowchart
        2.2.6 Executable
        2.2.7 Code Generation
    2.3 NONFUNCTIONAL REQUIREMNENT
        2.3.1 Reliability:
        2.3.2 Performance:
        2.3.3 Maintainability:
    2.4 SYSTEM REQUIREMENT
    2.5 Use Case
        2.5.1 Actor
    2.6 Use Case Diagram
        2.6.1 Make Block Diagram:
        2.6.2 Add Component
        2.6.3 Remove Component
        2.6.4 Link Connection
        2.6.5 Set Connection Properties
        2.6.6 Generate configuration code for Block Diagram
        2.6.7 Save Code
        2.6.8 Generate HEX file
        2.6.9 Modify Block Diagram
        2.6.10 Make Flow Chart
        2.6.11 Reset Connection Properties
        2.6.12 Modify Flowchart
3 CHAPTER 3–SYSTEM DESIGN
    3.1 SYSTEM DESIGN
    3.2 SYSTEM ARCHITECTURE
        3.2.1 Software Architecture
        3.2.2 System Architecture
    3.3 Activity diagram
        3.3.1 Generate Code
        3.3.2 Update Block Diagram
    3.4 Class Diagram
    3.5 Sequence Diagram
        3.5.1 Pic Component
        3.5.2 Draw Items
        3.5.3 Drag Device
        3.5.4 Set Property
        3.5.5 Remove Device
        3.5.6 Generate Code
    3.6 Collaboration Diagrams
        3.6.1 View Code
        3.6.2 Drag Device
        3.6.3 Generate Code
        3.6.4 Set Property
4 CHAPTER 4–IMPLEMENTATION
    4.1 Introduction
    4.2 Overall System Design
        4.2.1 Data Flow Graph Design
        4.2.2 System Function Module Design
    4.3 Tools and Technologies
    4.4 Reasons for using Tools specified:
    4.5 Software Components
        4.5.1 Presentation Layer
5 CHAPTER 5–IDE TESTING
    5.1 Introduction:
    5.2 Software Testing Axioms
    5.3 White box, black box, and grey box testing
    5.4 Test cases, suites, scripts and scenarios
    5.5 A sample testing cycle
    5.6 Test Cases
        5.6.1 Make Block Diagram
        5.6.2 Set Connection Properties
        5.6.3 Remove Component
        5.6.4 Generate Code for Block Diagram
    5.7 Calculator Case Study
Conclusion
    The Software at its Best
    Software Requirements
    Hardware Requirements
致謝ACKNOWLEDGEMENT
參考文獻(xiàn)References



本文編號(hào)：3228807