Status report #8
•Download as PPTX, PDF•
0 likes•147 views
The status report summarizes the work of Team #1 on their DC distribution controller project. They have completed constructing a prototype, ordering additional parts, and programming the microcontroller. Recent tasks include ordering more parts, drafting a final report, and testing sensors and converters. Ongoing tasks are communication with the charge controller, testing prototype parts, creating a demo day poster, analyzing energy efficiency performance, fabricating a demonstration, and preparing a presentation for a competition.
Report
Share
Report
Share
Recommended
Status report #7
The status report is for Team #1 and their DC Distribution Controller project. They have completed constructing a prototype, ordering additional parts, programming the microcontroller, and debugging and testing the design. Recent tasks include ordering more parts, drafting a final report, and testing current/voltage sensors and the DC/DC converter. Ongoing tasks are communication with the charge controller, testing prototype parts, creating a demo day poster, analyzing energy efficiency performance, fabricating the senior design demonstration, and preparing a presentation for a competition.
System Design
This document discusses architectural design and software architectures. It describes architectural design as representing the link between specification and design processes and involving identifying major system components and their communications. It discusses different types of architectural models including client-server, layered, object-oriented, and reference architectures. It also covers different approaches to system control structures.
Sdlc 4
The document discusses the system development life cycle (SDLC), which includes preliminary investigation, requirements analysis, system design, software development, system testing, and implementation and maintenance. It describes the purpose and history of SDLC as emerging in the 1960s to address the "software crisis". It also outlines the main steps and activities in each phase of the SDLC process.
Software Testing (Usability Testing of Website)
The document discusses various aspects of software testing including:
- The importance of testing to find errors and the limitations of testing.
- Good testing practices such as focusing on error detection, avoiding self-testing, and thoroughly inspecting test results.
- Different levels of testing from unit to acceptance testing.
- Methods for test planning, estimation, development of test cases and scripts, and reporting of results.
Software Testing
The document discusses various topics related to software testing including verification, validation, black box testing, white box testing, and different types of testing such as unit testing, integration testing, functional testing, system testing, stress testing, performance testing, usability testing, acceptance testing, regression testing, and beta testing. It provides definitions and descriptions of these key terms and explains whether each type of testing falls under black box or white box testing.
Software maintenance
This document discusses software maintenance and metrics used to measure software complexity. It notes that maintenance makes up 70% of a software's lifecycle costs. Common maintenance activities include enhancements, adaptations, and corrections. Two important source code metrics discussed are Halstead's effort equation and McCabe's cyclomatic complexity, which measure properties of source code like tokens and control flow to evaluate complexity. Maintaining complexity metrics is important during software evolution and maintenance.
Reverse Engineering.pptx
Reverse engineering is the process of extracting knowledge or design information from something to understand its workings or recreate it. It often involves disassembling hardware or software and analyzing components. Common tools used are disassemblers to convert binary to assembly code, debuggers to view program state, hex editors to view and edit binary, and decompilers to recreate source code from machine code. The document also discusses security risks of reverse engineering like information disclosure, spoofing, and code modification, as well as some famous legal cases involving reverse engineering.
Software maintenance ppt
The document discusses various aspects of software maintenance including:
1. Software maintenance is the modification of software after delivery to correct bugs, improve performance, or adapt to changes. It includes activities like corrective, perfective, adaptive, and preventive maintenance.
2. Important reasons for software maintenance include adapting to changing environments, fixing bugs, and improving performance with upgrades.
3. Common software maintenance models include the quick fix model, iterative enhancement model, reuse model, Boehm's model, and Taute maintenance model. Each has different processes and advantages.
Recommended
Status report #7
The status report is for Team #1 and their DC Distribution Controller project. They have completed constructing a prototype, ordering additional parts, programming the microcontroller, and debugging and testing the design. Recent tasks include ordering more parts, drafting a final report, and testing current/voltage sensors and the DC/DC converter. Ongoing tasks are communication with the charge controller, testing prototype parts, creating a demo day poster, analyzing energy efficiency performance, fabricating the senior design demonstration, and preparing a presentation for a competition.
System Design
This document discusses architectural design and software architectures. It describes architectural design as representing the link between specification and design processes and involving identifying major system components and their communications. It discusses different types of architectural models including client-server, layered, object-oriented, and reference architectures. It also covers different approaches to system control structures.
Sdlc 4
The document discusses the system development life cycle (SDLC), which includes preliminary investigation, requirements analysis, system design, software development, system testing, and implementation and maintenance. It describes the purpose and history of SDLC as emerging in the 1960s to address the "software crisis". It also outlines the main steps and activities in each phase of the SDLC process.
Software Testing (Usability Testing of Website)
The document discusses various aspects of software testing including:
- The importance of testing to find errors and the limitations of testing.
- Good testing practices such as focusing on error detection, avoiding self-testing, and thoroughly inspecting test results.
- Different levels of testing from unit to acceptance testing.
- Methods for test planning, estimation, development of test cases and scripts, and reporting of results.
Software Testing
The document discusses various topics related to software testing including verification, validation, black box testing, white box testing, and different types of testing such as unit testing, integration testing, functional testing, system testing, stress testing, performance testing, usability testing, acceptance testing, regression testing, and beta testing. It provides definitions and descriptions of these key terms and explains whether each type of testing falls under black box or white box testing.
Software maintenance
This document discusses software maintenance and metrics used to measure software complexity. It notes that maintenance makes up 70% of a software's lifecycle costs. Common maintenance activities include enhancements, adaptations, and corrections. Two important source code metrics discussed are Halstead's effort equation and McCabe's cyclomatic complexity, which measure properties of source code like tokens and control flow to evaluate complexity. Maintaining complexity metrics is important during software evolution and maintenance.
Reverse Engineering.pptx
Reverse engineering is the process of extracting knowledge or design information from something to understand its workings or recreate it. It often involves disassembling hardware or software and analyzing components. Common tools used are disassemblers to convert binary to assembly code, debuggers to view program state, hex editors to view and edit binary, and decompilers to recreate source code from machine code. The document also discusses security risks of reverse engineering like information disclosure, spoofing, and code modification, as well as some famous legal cases involving reverse engineering.
Software maintenance ppt
The document discusses various aspects of software maintenance including:
1. Software maintenance is the modification of software after delivery to correct bugs, improve performance, or adapt to changes. It includes activities like corrective, perfective, adaptive, and preventive maintenance.
2. Important reasons for software maintenance include adapting to changing environments, fixing bugs, and improving performance with upgrades.
3. Common software maintenance models include the quick fix model, iterative enhancement model, reuse model, Boehm's model, and Taute maintenance model. Each has different processes and advantages.
Walsh, Stephani - Resume
This document is a resume for Stephani Walsh, who is seeking an electrical engineering position. She has over 5 years of experience as an intern and contractor at Lockheed Martin and GE Aviation, where she performed systems engineering, requirements engineering, testing, and integration work. She has skills in requirements management tools like DOORS, modeling tools like Visio, programming languages like C++, and engineering tools like Matlab. She has a Bachelor's degree in Electrical Engineering from the University of South Florida.
How To Avoid Continuously Delivering Faulty Software
As organizations continue to compress development and delivery lifecycles, the risk of regressions, integration errors, and other defects rises. But how can development teams integrate defect prevention strategies into their release cycles to ensure that they're not continuously delivering faulty software? In this presentation, learn the key development testing processes to add to your Continuous Delivery system to reduce the risk of automating the release of software defects.
Bug hunting through_reverse_engineering
The document discusses reverse engineering techniques for bug hunting and exploit development. It covers analyzing software, hardware, applications, operating systems and firmware through static and dynamic reverse engineering. Static techniques include disassembling and analyzing binary code while dynamic techniques involve emulating or debugging running programs. The document also discusses fuzzing techniques, common bug classes, challenges like obfuscated code, and tools like LLVM and LibFuzzer that can be used for reverse engineering and fuzzing. The overall goal of reverse engineering discussed is to develop exploits by finding and analyzing bugs, whether to develop without source code, bypass restrictions, or for malware analysis and curiosity.
Xia Emma Yang Resume
This document is a resume for Xia (Emma) Yang, summarizing her qualifications and experience in user interface, regression, and firmware testing. She has over eight years of experience as a Product Test Engineer, testing hardware and software for companies like Samsung, LG, Motorola, Microsoft, BMW, GE, and Boeing. Her technical skills include hardware testing, Lean Manufacturing methodology, databases, and tools like oscilloscopes. She worked for Data I/O Corporation for over 15 years as a Test Engineer, Electrical Engineer, and Electronic Engineer, setting up testing platforms and writing test cases and procedures. She holds a BSEE from Beijing University of Post and Telecommunications.
Il product development - 20 01 2011
The document describes INDePT, an agile product development methodology used by Innovation Lab LLC. The methodology consists of three phases (analysis, design and development, rollout) containing multiple iterations. The analysis phase includes problem domain analysis and functionality analysis. The design phase includes system design, prototyping, and feature development. A case study project called SOPRAX is also described, which was a social networking and e-commerce website. Tools used in the methodology include Java, Maven, JUnit, Subversion, Confluence, and MS Project. Metrics are collected throughout the process to monitor progress.
A presentation on software maintenanace
This presentation summarizes software maintenance. It defines software maintenance as modifying software after delivery to fix bugs, improve performance, or adapt to changes. The main types of maintenance are corrective, adaptive, perfective, and preventive maintenance. Corrective maintenance fixes bugs, adaptive maintenance adapts software to new environments, perfective maintenance improves performance, and preventive maintenance finds latent bugs. Maintenance costs are typically much higher than development costs. Common maintenance problems include lack of documentation and software not designed for change. The presentation also discusses errors, faults, downtime, and the importance of documentation.
Deepthi Resume-TM
Shanthi Deepthi K has over 8 years of experience as an electronics engineer specializing in component engineering and testing. She has worked for several major companies, including TechMahindra where she verified component suppliers and identified obsolete components. She also worked at Google as an operations lead, preparing training modules and reports. Deepthi has a bachelor's degree in electronics engineering and is proficient in several programming languages and databases.
12 software maintenance
Here are the key points to cover in your homework:
1. Factors affecting maintenance cost include:
- Module independence
- Programming language
- Programming style
- Quality of testing
- Documentation
- Staff stability
- Age of system
2. Types of maintenance are:
- Corrective
- Adaptive
- Perfective
- Preventative
3. Lehman's Laws describe how software evolves over time in a real-world environment. The five laws cover continuing change, increasing complexity, self-regulating evolution, constant development rate, and familiarity.
4. The maintenance process involves change management, impact analysis, release planning, change implementation, and system release. It aims to efficiently
Sdlc
This document provides an overview of the software development life cycle (SDLC) or project life cycle (PLC). It describes the typical phases of the SDLC, including feasibility analysis, planning, requirements specification, design, coding, testing, deployment, and maintenance. For each phase, it outlines the key activities, deliverables, and responsible roles. The overall SDLC is presented as a structured process to develop software, from initial requirements through maintenance of the completed system.
Software reuirement elicitation in software engineering basics by ram k paliwal
these slides include the software requirement elicitation technique to gather requirement form different sources
Performance Bottleneck Identification through Software Diagnostics- Impetus W...
Performance Bottleneck Identification through Software Diagnostics- Impetus W...Impetus Technologies
The document discusses diagnostic tools for identifying software performance bottlenecks. It outlines typical processes for bottleneck identification, how diagnostic tools work, usage scenarios for server-side and client-side diagnostics, benefits of diagnostic tools, and real-world examples. Diagnostic tools provide response time breakdowns across tiers and components to isolate costly queries and memory leaks. Both plug-in and custom diagnostic tools are described, along with approaches for mobile and browser diagnostics.Function Point Analysis
Function point analysis is a method of estimating the size of a software or system by counting the number of inputs, outputs, inquiries, internal logical files and external interface files. It was introduced in 1979 as an alternative to simply counting lines of code. Function point analysis measures the software based on end user requirements rather than implementation details. It provides a consistent way to measure software across different projects, organizations and programming languages. The document provides an overview of function point analysis including its history, why it is needed, how it works and how it is used to estimate sizes of major software applications.
Pinpointing and Exploiting Specific Performance Bottlenecks
Explore how to move from raw data to action by pinpointing and exploiting specific bottlenecks collaboratively.
Waterfall model
The waterfall model is a sequential design process for software engineering projects consisting of conception, initiation, analysis, design, construction, testing, production, and maintenance phases. It works best when requirements are stable, the project is small, the environment is stable, and trained resources are available. Key advantages include adapting team shifts, forcing structured organizations, and allowing for early design changes, while disadvantages are nonadaptive design constraints, ignoring mid-process feedback, and delayed testing.
formal verification
Formal verification refers to mathematical techniques for specifying, designing, and verifying software and hardware systems. It involves proving or disproving the correctness of algorithms in a system with respect to a formal specification or property using formal methods of mathematics. Formal verification techniques include manual proofs, semi-automatic theorem proving, and automatic algorithms that take a model and property to determine if the model satisfies the property. Formal verification is commonly used for safety-critical systems like embedded systems to help ensure correctness. Tools like VC formal, VC LP, and Spyglass can be used to formally verify designs early in development without complex test benches or stimulus.
Performance Testing of eLearning Portal- A case study by Oak Systems Pvt Ltd
This case study is about Performance Testing carried out on elearning portal. The portal was developed using open source and evolved functionalities and Graphical User Interface. Oak Team successfully completed testing involving,collecting various metrics and identifying Server and Portal capabilities,execution of tests across various bandwidths,Virtual users.
Function Points
Function point analysis is a method of estimating the size of a software application based on the user view rather than lines of code. It involves identifying and classifying functional components such as internal logical files, external interface files, inputs, outputs, and inquiries. Each component is assigned a complexity and weight to calculate the total functional size in function points. The size can then be adjusted based on 14 general system characteristics to determine the final adjusted size. The document provides details on the history, vocabulary, types of data and transactions, counting process, and complexity determination involved in function point analysis.
Ch 8 configuration management
The document discusses software configuration management. It describes version 1.0 and 1.1 of a software engineering document released on February 2, 2012 and June 2, 2012 respectively by author Kittitouch S. Version 1.1 added details on software configuration versions, tools for managing configuration, and a software configuration management plan. The document then discusses software configuration, management, and control as well as accurate versioning. It describes configuration items, versions, and numerating conventions. The summary provides an overview of the key topics and changes covered in the document.
Software reliability tools and common software errors
The document discusses various software reliability tools and common software errors. It describes tools like SMERFS, SRMP, SoftRel, and CASRE which are used for statistical modeling and estimation of software reliability. SMERFS is designed to estimate and predict reliability during testing using failure data. SRMP contains nine models and uses maximum likelihood estimation. SoftRel simulates project occurrences using a Piecewise-Poisson Markov Process. CASRE was developed by NASA to make reliability estimation easier. Common software errors discussed include errors in handling, preventing, detecting and recovering from errors, as well as boundary, calculation, initial state, race condition and load condition errors.
Software quality
The document discusses software quality and defines key aspects:
- It explains the importance of software quality for users and developers.
- Qualities like correctness, reliability, efficiency are defined.
- Methods for measuring qualities like ISO 9126 standard are presented.
- Quality is important throughout the software development process.
- Both product quality and process quality need to be managed.
Status report #6
Team #1 is designing a system to take energy from solar PV arrays and batteries and distribute it safely through a DC circuit using a controller. They recently tested a DC-DC converter and ordered additional parts. Upcoming tasks include developing a microcontroller algorithm, further testing prototype parts and the DC-DC converter, fabricating a senior design demo, and testing battery charging with the prototype.
More Related Content
What's hot
Walsh, Stephani - Resume
This document is a resume for Stephani Walsh, who is seeking an electrical engineering position. She has over 5 years of experience as an intern and contractor at Lockheed Martin and GE Aviation, where she performed systems engineering, requirements engineering, testing, and integration work. She has skills in requirements management tools like DOORS, modeling tools like Visio, programming languages like C++, and engineering tools like Matlab. She has a Bachelor's degree in Electrical Engineering from the University of South Florida.
How To Avoid Continuously Delivering Faulty Software
As organizations continue to compress development and delivery lifecycles, the risk of regressions, integration errors, and other defects rises. But how can development teams integrate defect prevention strategies into their release cycles to ensure that they're not continuously delivering faulty software? In this presentation, learn the key development testing processes to add to your Continuous Delivery system to reduce the risk of automating the release of software defects.
Bug hunting through_reverse_engineering
The document discusses reverse engineering techniques for bug hunting and exploit development. It covers analyzing software, hardware, applications, operating systems and firmware through static and dynamic reverse engineering. Static techniques include disassembling and analyzing binary code while dynamic techniques involve emulating or debugging running programs. The document also discusses fuzzing techniques, common bug classes, challenges like obfuscated code, and tools like LLVM and LibFuzzer that can be used for reverse engineering and fuzzing. The overall goal of reverse engineering discussed is to develop exploits by finding and analyzing bugs, whether to develop without source code, bypass restrictions, or for malware analysis and curiosity.
Xia Emma Yang Resume
This document is a resume for Xia (Emma) Yang, summarizing her qualifications and experience in user interface, regression, and firmware testing. She has over eight years of experience as a Product Test Engineer, testing hardware and software for companies like Samsung, LG, Motorola, Microsoft, BMW, GE, and Boeing. Her technical skills include hardware testing, Lean Manufacturing methodology, databases, and tools like oscilloscopes. She worked for Data I/O Corporation for over 15 years as a Test Engineer, Electrical Engineer, and Electronic Engineer, setting up testing platforms and writing test cases and procedures. She holds a BSEE from Beijing University of Post and Telecommunications.
Il product development - 20 01 2011
The document describes INDePT, an agile product development methodology used by Innovation Lab LLC. The methodology consists of three phases (analysis, design and development, rollout) containing multiple iterations. The analysis phase includes problem domain analysis and functionality analysis. The design phase includes system design, prototyping, and feature development. A case study project called SOPRAX is also described, which was a social networking and e-commerce website. Tools used in the methodology include Java, Maven, JUnit, Subversion, Confluence, and MS Project. Metrics are collected throughout the process to monitor progress.
A presentation on software maintenanace
This presentation summarizes software maintenance. It defines software maintenance as modifying software after delivery to fix bugs, improve performance, or adapt to changes. The main types of maintenance are corrective, adaptive, perfective, and preventive maintenance. Corrective maintenance fixes bugs, adaptive maintenance adapts software to new environments, perfective maintenance improves performance, and preventive maintenance finds latent bugs. Maintenance costs are typically much higher than development costs. Common maintenance problems include lack of documentation and software not designed for change. The presentation also discusses errors, faults, downtime, and the importance of documentation.
Deepthi Resume-TM
Shanthi Deepthi K has over 8 years of experience as an electronics engineer specializing in component engineering and testing. She has worked for several major companies, including TechMahindra where she verified component suppliers and identified obsolete components. She also worked at Google as an operations lead, preparing training modules and reports. Deepthi has a bachelor's degree in electronics engineering and is proficient in several programming languages and databases.
12 software maintenance
Here are the key points to cover in your homework:
1. Factors affecting maintenance cost include:
- Module independence
- Programming language
- Programming style
- Quality of testing
- Documentation
- Staff stability
- Age of system
2. Types of maintenance are:
- Corrective
- Adaptive
- Perfective
- Preventative
3. Lehman's Laws describe how software evolves over time in a real-world environment. The five laws cover continuing change, increasing complexity, self-regulating evolution, constant development rate, and familiarity.
4. The maintenance process involves change management, impact analysis, release planning, change implementation, and system release. It aims to efficiently
Sdlc
This document provides an overview of the software development life cycle (SDLC) or project life cycle (PLC). It describes the typical phases of the SDLC, including feasibility analysis, planning, requirements specification, design, coding, testing, deployment, and maintenance. For each phase, it outlines the key activities, deliverables, and responsible roles. The overall SDLC is presented as a structured process to develop software, from initial requirements through maintenance of the completed system.
Software reuirement elicitation in software engineering basics by ram k paliwal
these slides include the software requirement elicitation technique to gather requirement form different sources
Performance Bottleneck Identification through Software Diagnostics- Impetus W...
Performance Bottleneck Identification through Software Diagnostics- Impetus W...Impetus Technologies
The document discusses diagnostic tools for identifying software performance bottlenecks. It outlines typical processes for bottleneck identification, how diagnostic tools work, usage scenarios for server-side and client-side diagnostics, benefits of diagnostic tools, and real-world examples. Diagnostic tools provide response time breakdowns across tiers and components to isolate costly queries and memory leaks. Both plug-in and custom diagnostic tools are described, along with approaches for mobile and browser diagnostics.Function Point Analysis
Function point analysis is a method of estimating the size of a software or system by counting the number of inputs, outputs, inquiries, internal logical files and external interface files. It was introduced in 1979 as an alternative to simply counting lines of code. Function point analysis measures the software based on end user requirements rather than implementation details. It provides a consistent way to measure software across different projects, organizations and programming languages. The document provides an overview of function point analysis including its history, why it is needed, how it works and how it is used to estimate sizes of major software applications.
Pinpointing and Exploiting Specific Performance Bottlenecks
Explore how to move from raw data to action by pinpointing and exploiting specific bottlenecks collaboratively.
Waterfall model
The waterfall model is a sequential design process for software engineering projects consisting of conception, initiation, analysis, design, construction, testing, production, and maintenance phases. It works best when requirements are stable, the project is small, the environment is stable, and trained resources are available. Key advantages include adapting team shifts, forcing structured organizations, and allowing for early design changes, while disadvantages are nonadaptive design constraints, ignoring mid-process feedback, and delayed testing.
formal verification
Formal verification refers to mathematical techniques for specifying, designing, and verifying software and hardware systems. It involves proving or disproving the correctness of algorithms in a system with respect to a formal specification or property using formal methods of mathematics. Formal verification techniques include manual proofs, semi-automatic theorem proving, and automatic algorithms that take a model and property to determine if the model satisfies the property. Formal verification is commonly used for safety-critical systems like embedded systems to help ensure correctness. Tools like VC formal, VC LP, and Spyglass can be used to formally verify designs early in development without complex test benches or stimulus.
Performance Testing of eLearning Portal- A case study by Oak Systems Pvt Ltd
This case study is about Performance Testing carried out on elearning portal. The portal was developed using open source and evolved functionalities and Graphical User Interface. Oak Team successfully completed testing involving,collecting various metrics and identifying Server and Portal capabilities,execution of tests across various bandwidths,Virtual users.
Function Points
Function point analysis is a method of estimating the size of a software application based on the user view rather than lines of code. It involves identifying and classifying functional components such as internal logical files, external interface files, inputs, outputs, and inquiries. Each component is assigned a complexity and weight to calculate the total functional size in function points. The size can then be adjusted based on 14 general system characteristics to determine the final adjusted size. The document provides details on the history, vocabulary, types of data and transactions, counting process, and complexity determination involved in function point analysis.
Ch 8 configuration management
The document discusses software configuration management. It describes version 1.0 and 1.1 of a software engineering document released on February 2, 2012 and June 2, 2012 respectively by author Kittitouch S. Version 1.1 added details on software configuration versions, tools for managing configuration, and a software configuration management plan. The document then discusses software configuration, management, and control as well as accurate versioning. It describes configuration items, versions, and numerating conventions. The summary provides an overview of the key topics and changes covered in the document.
Software reliability tools and common software errors
The document discusses various software reliability tools and common software errors. It describes tools like SMERFS, SRMP, SoftRel, and CASRE which are used for statistical modeling and estimation of software reliability. SMERFS is designed to estimate and predict reliability during testing using failure data. SRMP contains nine models and uses maximum likelihood estimation. SoftRel simulates project occurrences using a Piecewise-Poisson Markov Process. CASRE was developed by NASA to make reliability estimation easier. Common software errors discussed include errors in handling, preventing, detecting and recovering from errors, as well as boundary, calculation, initial state, race condition and load condition errors.
Software quality
The document discusses software quality and defines key aspects:
- It explains the importance of software quality for users and developers.
- Qualities like correctness, reliability, efficiency are defined.
- Methods for measuring qualities like ISO 9126 standard are presented.
- Quality is important throughout the software development process.
- Both product quality and process quality need to be managed.
What's hot (20)
How To Avoid Continuously Delivering Faulty Software
How To Avoid Continuously Delivering Faulty Software
Software reuirement elicitation in software engineering basics by ram k paliwal
Software reuirement elicitation in software engineering basics by ram k paliwal
Performance Bottleneck Identification through Software Diagnostics- Impetus W...
Performance Bottleneck Identification through Software Diagnostics- Impetus W...
Pinpointing and Exploiting Specific Performance Bottlenecks
Pinpointing and Exploiting Specific Performance Bottlenecks
Performance Testing of eLearning Portal- A case study by Oak Systems Pvt Ltd
Performance Testing of eLearning Portal- A case study by Oak Systems Pvt Ltd
Software reliability tools and common software errors
Software reliability tools and common software errors
More from gtrevino80
Status report #6
Team #1 is designing a system to take energy from solar PV arrays and batteries and distribute it safely through a DC circuit using a controller. They recently tested a DC-DC converter and ordered additional parts. Upcoming tasks include developing a microcontroller algorithm, further testing prototype parts and the DC-DC converter, fabricating a senior design demo, and testing battery charging with the prototype.
Status report #5
Team #1 is designing a system to control and distribute DC power from solar panels to a DC circuit. They constructed a DC controller prototype, ordered additional parts, and planned their senior design demonstration. Upcoming tasks include finalizing their DC to DC converter design and fabricating their senior design demo.
Status report #4
Team #1 submitted their status report #4 on their project to design a DC distribution controller system. They have ordered remaining parts to be delivered by February 6th and will test and verify parts by February 12th. They will construct a prototype by February 20th and order any additional parts needed by February 27th. They will finalize the microcontroller programming for the system by March 10th.
Status report #3
Team #1 submitted their status report #3 on their project to design a DC distribution controller system. They have ordered remaining parts to be delivered by February 6th and will test and verify parts by February 12th. They will construct a prototype by February 20th and order any additional parts needed by February 27th. They will finalize the microcontroller programming for the system by March 10th.
Status report #2
The team is working on a DC distribution controller to directly use free energy from solar panels without converting to AC. Recent tasks included finishing competition papers and proposals. Ongoing tasks involve economic analysis, design documentation, and simulations. Upcoming milestones are finalizing the competition paper, product selection, and building a prototype by purchasing parts in February and March.
Status report #1
The team is working on a DC distribution controller to directly use free energy from solar panels without converting to AC. Their recent tasks included finishing an outline for an IEEE competition paper and meeting with a mentor. Upcoming tasks are to finish the competition paper, finalize the product selection list, and purchase products to build a prototype. Their schedule includes buying parts by January 10th, building a prototype by February, and programming an FPGA/microcontroller by March 5th.
More from gtrevino80 (7)
Status report #8
- 1. Team #1 Javier Guerrero Jeremy Halbardier Olakunle Sosanya Gerardo Trevino DC DISTRUBUTION CONTROLLER STATUS REPORT #8 04/07/2010
- 2. Completed Tasks Construct DC Controller Prototype Order Additional Parts Needed Program for Microcontroller Debug and test of the design
- 3. Recent tasks Order Additional Parts Needed Draft Final Report Current/ voltage sensors test DC/DC converter test Improve algorithm
- 4. Ongoing/Pending Tasks Charge Controller Communication Testing prototype parts. Demo Day Poster Analyze Energy Efficiency System Performance Fabricate Sr. Design Demo Presentation CCET-IEEE competition
- 6. Questions