Scribd
Upload
0 views

Mid Semester Progress Report COOP2

The project report details the progress of a co-op project in embedded software development, following the V-Model software development cycle. Key milestones include requirement analysis, architecture design, detailed design and implementation, and ongoing testing phases, with a focus on achieving industry standards. The report highlights the use of various development tools and techniques, along with significant achievements in structured software development and teamwork.

Uploaded by

chhayayadav17072003
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 views

Mid Semester Progress Report COOP2

The project report details the progress of a co-op project in embedded software development, following the V-Model software development cycle. Key milestones include requirement analysis, architecture design, detailed design and implementation, and ongoing testing phases, with a focus on achieving industry standards. The report highlights the use of various development tools and techniques, along with significant achievements in structured software development and teamwork.

Uploaded by

chhayayadav17072003
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

PROJECT REPORT OF CO-OP PROJECT AT INDUSTRY (MODULE-2)

ON

MFL Std.
Mid- Semester Progress Report

BACHELOR OF ENGINEERING

In

COMPUTER SCIENCE AND ENGINEERING

Submitted by: Supervised By:

Chhaya Yadav Avneet Singh Bassi

2110991886 H.O.D

Hella Forvia

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CHITKARA UNIVERSITY

CHANDIGARH-PATIALA NATIONAL HIGHWAY, RAJPURA, PUNJAB, INDIA

1
CONTENTS

Title Page No.

1. Project Milestones 03
2. In Progress 04
3. Tools Techniques Used 04
4. Key Achievements and Learning 05-06

2
1. Project Milestones
The project follows the V-Model software development cycle, ensuring structured
progress and verification at every phase. Below are the key milestones achieved along with
their completion dates:

1.1.Requirement Analysis (Week 1-2)

 Completion Date: January 24, 2025


 Collected and analyzed system requirements.
 Defined the project scope and constraints.
 Created the Software Requirement Specification (SRS) document.

1.2.Architecture Design (Week 3-5)

 Completion Date: February 14, 2025


 Developed a modular and scalable system architecture.
 Selected the appropriate technology stack and tools.
 Designed Data Flow Diagrams (DFDs) and Entity-Relationship Diagrams (ERDs)
to define system interactions.

1.3.Detailed Design & Implementation (Week 6-9)

 Completion Date: March 7, 2025


 Designed individual modules for implementation.
 Started coding following best practices and coding standards.
 Conducted code reviews and developed unit test cases.

1.4.Unit Testing (Week 10-11)

 Target Completion Date: March 21, 2025


 Conducted unit tests to verify individual components and ensure expected
functionality.
 Used automated and manual testing to identify and resolve bugs.
 Improved performance through optimization techniques.

3
2. In Progress
The project is currently in the testing and integration phase, ensuring the software meets
industry standards.

2.1.Integration & System Testing (Week 12-14)

 Target Completion Date: April 11, 2025


 Merging individual modules and performing functional and performance testing.
 Ensuring stability, security, and compliance with project requirements.
 Conducting stress and reliability tests for system validation.

2.2.Final Qualification & Documentation (Week 15-16)

 Target Completion Date: April 25, 2025


 Performing final validation and user acceptance testing.
 Addressing any remaining issues and optimizing system performance.
 Preparing final documentation and deployment guidelines.

2.3.Required Resources

 Testing Environments: Access to automated testing tools (Tessy, Canoe).


 Debugging Support: Continued use of IAR Workbench and Meleis IDE.
 Team Collaboration: Coordination with developers and testers for smooth integration.

3. Tools and Techniques Used


The project utilizes industry-standard tools to enhance software development efficiency and
ensure compliance with best practices.

3.1.Development and Testing Tools

 IAR Workbench: Provides a comprehensive environment for embedded software


development and debugging, used for writing and testing firmware.

4
 Rhapsody: A model-driven development tool used for system design and simulation,
ensuring a structured architecture.
 Canoe: Used for simulating and testing automotive Electronic Control Units (ECUs)
to ensure compliance with industry standards.
 Tessy: An automated testing tool that performs unit testing and validation, helping
identify and resolve errors in the early development phases.
 Meleis IDE: An integrated development environment that streamlines software
development, compilation, and debugging processes.

These tools help in reducing defects, improving system reliability, and ensuring smooth
project execution.

4. Key Achievements
The project has made significant progress, achieving several milestones that enhance system
reliability and performance.

4.1.Understanding of ASPICE Standards

 Gained hands-on experience with ASPICE-compliant software development.


 Ensured structured verification and validation throughout the project.

4.2.Enhanced Debugging and Troubleshooting Skills

 Worked extensively on debugging embedded software to resolve critical issues.


 Used Rhapsody and Tessy to simulate system behavior and identify defects early.

4.3.Structured Software Development Experience

 Successfully implemented the V-Model to ensure systematic development.


 Verified each phase before progressing, reducing the risk of defects.

5
4.4.Improved Teamwork and Collaboration

 Effectively coordinated with team members, mentors, and industry professionals.


 Maintained structured documentation and reporting for each project phase.

Conclusion
The project is progressing as planned, with initial phases successfully completed. The focus
now shifts to integration, final testing, and documentation. By following best practices and
using advanced development tools, the project aims to deliver a high-performance embedded
software system meeting industry standards.

You might also like