Software Engineering Clause Samples
POPULAR SAMPLE Copied 2 times
Software Engineering. Consultant agrees to assist the Company with creation and testing of the Software Component. Consultant will act only as a consultant and it is the responsibility of the Company and its affiliates to ensure the proper functioning of the software system and Software Component to be developed by the Consultant.
Software Engineering. Consultant agrees to assist the Company with creation and testing of the Software Component. Consultant will act only as a consultant and it is the responsibility of the Company and its affiliates to ensure the proper functioning of the software system and Software Component to be developed by the Consultant.
2. The retention by the Company of Consultant as heretofore described shall be for a period of not less than four months from the date hereof in order to provide Consultant a reasonable opportunity to perform its services (as outlined above). Following this four month period, this Agreement will automatically renew on a month-to-month basis unless terminated by either party upon 30 day advanced written notice.
3. Any parties introduced to the Company by Consultant, even if declining participation hereby, shall be deemed a "Protected Party" and thereafter the Company shall not directly deal with the Protected Party without the prior written consent of Consultant.
4. In connection with Consultant's activities on the Company's behalf, the Company will cooperate with Consultant and will furnish Consultant with all information and data concerning the Company (the "Information"), which Consultant deems appropriate and will provide Consultant with access to the Company's officers, directors, employees, independent accountants, and legal counsel. The Company represents and warrants that all Information made available to Consultant by the Company will, at all times during the period of engagement of Consultant hereunder, be complete and correct in all material respects and will not contain any untrue statement of a material fact or omit to state a material fact necessary in order to make the statements therein not misleading in the light of the circumstances under which such statements are made. The Company further represents and warrants that any software code provided by it to Consultant will have been prepared in good faith by the Company and is owned legally and completely by the Company. The Company acknowledges and agrees that, in rendering its services hereunder, Consultant may be using and relying on the Information without independent verification thereof by Consultant or independent appraisal by Consultant of any of the Company's assets. Consultant does not assume responsibility for any information regarding the Company. Any recommendations rendered by Consultant pursuant to this Agreement may not be disclosed publicly without our prior written conse...
Software Engineering. The Contractor shall provide software engineering support (including planning, analysis, design, evaluation, testing, quality assurance, and project management) in the application of computer equipment through computer programs, procedures, tools, and associated documentation. C.12.2.8.1 Software Quality Assurance
Software Engineering. The contractor shall provide general software engineering support as required for the design, prototyping, and implementation of SSG trainer products. This shall include documentation of software coding and use of software configuration management tools to ensure all software modifications are managed and committed to source code repositories at NSWCCD.
Software Engineering. The GCSS-MC PMO requires disciplined software engineering as an integral component of the overarching systems engineering approach needed to sustain the GCSS-MC Increment 1 system. The Contractor shall employ the use of sound software engineering principles, methods, practices, and tools to produce and sustain reliable GCSS- MC/LCM Increment 1 applications and associated RICECPW objects in an economical manner. GCSS-MC/LCM Increment 1 currently employs a modified agile development methodology for application sustainment. However, the Contractor may employ the approach that best meets the requirements to deliver reliable, high quality and cost effective software solutions. The Contractor shall perform disciplined application development activities consistent with CMMI Level 3.
Software Engineering. How to Assess: Several checklists have been developed to assess the maturity level. Term used to name of the Attributes: Fundamental Factors. Attributes (4): People; Technology; Process; Organization. Level Name Description
Software Engineering. When a requirement is established to provide software Engineering, the Contractor shall accomplish all or part of the following efforts to the degree specified in the order or task:
Software Engineering. The MyMedsTracker SMART on FHIR app must be able to store various types and formats of data including Pharmacy records, Prescription medication instructions, Prescription medication photos, and potentially video recordings of medication times should the patient want that option. The app must also be able to send data to the EMR and receive notes from a provider, caregiver, or family member who can all access the app on their own phone or computer and then synchronize this data with the patient’s stored record before the record is sent to the EMR weekly.
Software Engineering. The STE and its accompanying software components were programmed in Python. The reason for this is Python being a versatile and widely used programming language that favors readability, has an extensive library ecosystem and allows for rapid prototyping due to its simplicity. For the HTTP backend we chose FastAPI. It is a high-performance web framework for building REST APIs [Ram]. The reason for working with this framework is the build-in OpenAPI schema which is automatically generated with a UI documentation, including Swagger UI. It also provides automatic data validation via the Pydantic library. Even though Python is a dynamically typed language, meaning that the type of a variable is determined only during run time, Pydantic enforces type annotation throughout the code base and thus serves as a guideline for a clean code approach. It allows for some sort of static typing that compiled languages like Rust, Go or C offer without the need of relying on compilation and purely use the Python interpreter for validation. Accordingly, we were able to still use Python and its merits while at the same time being able to avoid demerits that interpreted languages have. We chose Pytest as our testing framework. Its ease of use allows for sophisticated and highly customizable unit tests enabling automated test execution and feedback loops during merge requests. This integration ensures that tests are consistently run and results are readily available for monitoring and ensuring integrity of our code base. The code base of the STE can be found in DECICE GitHub repository [DEC]. Each service within the STE runs as a micro service in a containerized environment. This design decision was made to give every partner the flexibility to choose their own approach when imple- ▇▇▇▇▇▇▇ software features. While some components are easier to develop in Python, others might benefit from a different language. Especially in the field scheduling decisions Go is often times a preferred candidate. Each micro service receives and sends data via HTTP requests in the form of CRUD operations [Moz]. On one hand this allows for an independent development of each software component and on the other hand each service is encapsulated and has its own boundaries to operate without affecting others on a large scale when changes are done.
Software Engineering. The contractor shall develop or review Specifications, Engineering Change Proposals (ECPs) and Notices Of Revision (NORs) for existing and new software or firmware development for one or more of the EW systems specified in Section 3 of this SOW. Documents shall be prepared for Government review and no changes shall be implemented without Government approval. Contractor developed Specifications shall be submitted IAW CDRL A004 Technical Report - Study/Services. Contractor developed ECPs shall be submitted IAW CDRL A005 Engineering Change Proposal (ECP) Class I ECP, and contractor developed NORs shall be submitted IAW CDRL A006 Notice of Revision (NOR).
