Software Engineering Sample Clauses

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.
AutoNDA by SimpleDocs
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. ‌ 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- xxxxxxx 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 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. Spring Semester 6 CIS 216 Problem Solving in OOP CIS 217 Intro to Unix CIS 290 Intro to Networks MATH 312 Probability and Statistics MATH 222 Discrete Math 1 Literature 1 3 CIS 350 Requirements & Proj. Mgmt. 3 CIS 255 Intro to Database 3 CIS 286 Object Oriented Programming 3 CIS 310 Software Design & Test 3 17 CIS 302 CIS Professional Seminar MATH 223 Discrete Math 2 CIS 303 Leadership Seminar
AutoNDA by SimpleDocs
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. Table 38. Summary of the Metrics Based Verification and Validation Maturity Model levels Level Name Description 1 Initial V&V shows that software products work. V&V is performed in an individual and ad-hoc way when time allows and only after coding. V&V works by finding and correcting issues, there is a lack of resources, tools and trained staff.
Software Engineering. Applications developed, maintained, and/or sustained are included in Appendix 7 - Software Applications Listing. Software engineering support is also provided to mainframe applications housed in the Xxxxxxxx Space Flight Center (MSFC) NASA Data Center (NDC). The operation and maintenance of the mainframe is not part of this contract. The NDC Computer System is an IBM Z9 Processor as outlined in the Office of Space Flight (OSF) Automatic Data Processing (ADP) Consolidations Concepts Document and KSC’s share is known as K14 LPAR (logical partition). Applications provided by the mainframe include: Human Resources, Financial Management, Equipment Management, Procurement Systems, etc. Email is sent every weekday indicating the status of backups for the systems identified by the Government. If the backup did not occur, an explanation is included documenting what is being done to resolve the issue. An Associate Account Authorization Official (aAAO) for the NASA Account Management System (NAMS) provides help desk support for users with NAMS accounts. The aAAO will be responsible for users’ local support, for entering the date the subscriber agreement is signed, the date when the IT Security Training was taken by the user, and for researching information on new account requests. These custom applications are developed and maintained using various programming languages and standard applications including: • Adobe Cold Fusion Version 5 and higher • Adobe Dreamweaver Version MX • Adobe Flash Version MX • Adobe Photoshop Version CS • Adobe Premiere Version CS • ASP, XXX.XXX, and .Net Frame work support • Autodesk 3D Studio MAX • Veritas Backup Exec • C, C++, C# • Clipper • CSS Flash • ESRI ArcGIS • FORTRAN • HTML • JAVA, JAVA Script, JAVA SVG • Mercury Test Director • Microsoft Internet Information Server Version 6 and higher • Microsoft Office Professional • Microsoft Operations Manager • Microsoft Project Version 2005 and higher • Microsoft Share Point Version 2 and higher • Microsoft SQL Server Version 2000 and higher • Microsoft WinBatch • Microsoft Windows Encoder • Microsoft Windows Media Server • MySQL • Nero • Norton Antivirus Corporate Edition • Oracle PL/SQL • PTC Pro/Engineer • PTC Windchill • Python • Real Networks Helix Server • Real Networks RealProducer • Select Business Solutions: NOMAD • Software AG ADABAS • Software AG “Natural” • Sound Forge Version 8 and higher • SpotLight • Visual Basic These systems support the services referenced in PWS 3.1.2.
Software Engineering. The Contractor shall design, develop, operate, and maintain software as it pertains to developmental flight testing of aircraft, aviation systems, UAS and associated aviation support equipment. The Contractor shall provide software engineering support in the reformatting and processing of Pulse Code Modulation (PCM), MIL-STD-1553 data (MIL-STD-1553 is provided for reference only), Aeronautical Radio, Incorporated 429, Ethernet, Universal Asynchronous Receiver-Transmitter, Video, Audio, Institute of Electrical and Electronics Engineers Standard 1394, serial data Time Space Position Information, analog, and discrete data. The Contractor shall provide support in the designing, coding, and debugging applications in multiple software languages such as C, C++, C- sharp, Visual Basic, Windows, and Structured Query Language to support the mission requirement. The Contractor shall document design software analysis, code analysis, requirements analysis, software review and identification of code metrics to support unique software applications that are used in the reduction and analysis of flight test data. Performance Standards STD: Accurate and timely direct test support within schedule and milestones as requested by the Government. AQL: 100% compliant with all regulations. 95% mission capable. Acceptable performance of this task requires the Contractor to perform direct test support functions and activities correctly and completely, with no more than 1 substantiated incident every six months. Deliverables A005 Work Products as requested A006 Data Reports and Documents as required
Time is Money Join Law Insider Premium to draft better contracts faster.