90 skills found · Page 2 of 3
presidio-oss / Hai BuildHAI Build is Presidio’s human-centric approach to harnessing Generative AI to produce faster, more collaborative, better-quality outcomes across the software development lifecycle. This groundbreaking innovation unlocks the ideal working relationship between human and machine.
NASA-AMMOS / SlimSoftware Lifecycle Improvement & Modernization
Dokuly-PLM / DokulyOpen Source Product Lifecycle Management Software
koki / KokiApplication Lifecycle Management Software
kcenon / Claude Code AgentAgent-Driven Software Development Lifecycle (AD-SDLC) system built with Claude Agent SDK
thecodeteam / Scaleio FrameworkThe ScaleIO Framework implements an Apache Mesos Framework to manage the lifecycle of ScaleIO, a scale-out software-based block storage platform.
guided-engineering / OpenPrompt Specification📘 Guided Engineering is a structured, traceable, and executable system for managing the entire software development lifecycle through modular prompts, intelligent agents, and reproducible documentation.
shubhamprajapati7748 / Sdlc CopilotSDLC Copilot is an Agentic AI system designed to streamline and automate the Software Development Lifecycle (SDLC). From requirement gathering to deployment and maintenance, SDLC Copilot leverages AI to optimize development workflows, reduce manual effort, and ensure software quality.
AZidan / ArchflowPhase-based AI development framework for Claude Code. Orchestrates 16+ specialized agents through the full software lifecycle.
naodeng / Awesome Qa PromptA professional collection of AI prompts for QA (Quality Assurance) professionals, designed to help test engineers and QA teams work more efficiently throughout the software testing lifecycle.
krzemienski / Claude Code BuilderAI-powered Python CLI tool that automates the entire software development lifecycle using the Claude Code SDK. From specification to deployment, Claude Code Builder
MedUnes / Dtrack CliA Go-based CLI tool to automate the upload and lifecycle management of Software Bill of Materials (SBOM) in OWASP Dependency-Track.
ideas4u / Trading PlatformThis project is the most awaited project in open source community where every user who belongs to Stock Trading always wanted to develop its own software. This project has been developed specifically for Indian Market Stock Trading. It encompasses end to end trading cycle for intraday trading but the design would be such that it can be easily extended for delivery trading. During the lifecycle of this project we will be using most advance technologies but the base code will always be C/C++. Development Methodology: ======================== We use "Incremental Life Cycle Model" along with Cross-Platform Development (Portable). Project Priorities and Assumptions: =================================== 1) Low Latency, High Performance all the time. 2) Wherever choice has to be made between memory and execution speed, we give preference to speed. 3) Every module devloped will be exhaustively tested. How the work Proceed: ===================== Before the beginning of any new project, we should know the "PROBLEM STATEMENT", so here it is "Problem Statement" ------------------- To Build a high performance, low latency, end to end Trading Platform for Indian Stock Market but not limited to which home users should be able use for trading which guarantees (99% of the times) the profit but does not guarantees maximized profit for intraday trading. First Step: ----------- To provide the optimal solution to any problem is "UNDERSTAING THE PROBLEM". To understand the above problem statement you need to really extract the explicit and implcit requirements from the statement. Here is the List of requirements: Explicit: --------- 1) High Performance 2) Low-Latency 3) End-to-End Trading Platform 4) Focus on Indian Stock Market but not limited to it. 5) Guarantees (99% of the times) the profit but does not guarantees maximized profit. 6) Only for Intraday Trading. Implicit: --------- 1) Book Keeping of the order and trade (Order Management System). 2) Availability of Market Data to End-Users on Demand for identifying the stock and placing the order. 3) User Account Management. Might be I missed something please suggest and after reveiw we add it here. Second Step: ------------ To understand the above Explicit/Implicit requirements, you should have the "KNOWLEDGE OF VARIOUS TECHNOLOGIES" and indepth undertstanding of the "PROBLEM DOMAIN" i.e. Stock Market. Once this is achieved we need to architect the solution in terms of Software and Hardware nodes and their integration. Third Step: ----------- To solve the problem statement, the above requirements should be "DECOMPOSED IN MODULES" and map to them with technolgoies/software/hardware used. Below is the list of modules we are able to identify: Modules Included: ================= Core Modules: -------------- 1) Core Libraries 2) Manual Order Entry System 3) Auto Order Entry System 4) Artificial Exchange 5) Algorithmic Trading Platform 6) Smart Order Router 7) Direct Trading Platform (Ooptional) Utility Modules: ---------------- 8) Logger Server 9) HeartBeat Server Technologies Used: ================= Software: --------- We always use freeware, Open Source Softwares or APIs which are the part of GPL, LGPL.xx licence. Any special requirement for building/using the modules will be detailed in specific module. For development, we generally use: ---------------------------------- Windows-7 for Operating System but any other OS ca be used. Our Code is Platform Indepandant. Visual Studio 2013 in built compiler for build or Intel@ Compilers which can be easily integrated with Visual Studio IDE. For real time, we generally use: -------------------------------- Linux-susse 10 or above with real time extensions. gcc 4.4.1 for build. vi editor Hardware: --------- No special requirement for development purpose. For real time use, it depands how much Stock you are interested in and the various configuration of modules. We prefer generally the below configuration for any number of Stock Trading: 256 GB RAM 16 core processor 1 TB of HDD/SDD Programming Languages and other Technologies: --------------------------------------------- C, C++99/c++11, Lua, ZeroMq, nanodbc, Lock-Free Data Structures, Intel TBB, Boost, Google Protobuf, MySql, Python. Fourth Step: ------------ Dcompose each module till it becomes entity to provide the useful functionality. We are going to explain this in each module detailed section. Fifth Step: ------------ We do design/develop/benchmark/unit test/integration testing of the above modules. Sixth Step: ------------ We deploy the delivered software on various hardware nodes as per the deployment architecture and integrate them. Seventh Step: ------------ Observe the behaviour of deployed software on live traffic and cut two branches at this level : 1st branch continue to do incremental development and 2nd branch fix the issues reported which can be later merged with 1st branch for another release. Any suggestions for improvement are most welcome.
atmb4u / Llm Coding WorfklowA structured methodology for using LLMs in the software development lifecycle
microsoft / Release Manager AssistantThe Release Manager Assistant (RMA) is an AI-powered solution accelerator that enhances the software release process by integrating multiple systems and providing real-time decision support. Designed to assist release managers, it streamlines the entire release lifecycle.
Kanjo-Elkamira-Ndi / SQA Lifecycle ImplementationFull Software Quality Assurance lifecycle implementation featuring modular banking systems, automated testing, version control with Git/GitFlow, and performance validation using Apache JMeter.
devarslanahmed / Software Project EstimatorSoftware Project Estimator helps in the estimation of size, effort, cost and development time of a project at different phases of design and implementation, that too, beforehand. The estimation will be done using three techniques; COCOMO I, COCOMO II and SLIM. All three of these accommodate different design process models. The motivation behind the project was to provide a single platform to the users for effective software estimation purposes. The website is a combination of three different estimation techniques; COCOMO1, COCOMO2 and SLIM that would estimate the size, effort, cost and development time beforehand. This will result in timely project submissions, quality work, adequate resources, and there would be less chances of project failure. Incremental methodology is used because of a number of reasons. A working software is obtained quickly and early during the software lifecycle. Risk management becomes easier because erroneous parts of the software are identified at each iteration. Smaller iterations enable easy testing and debugging and flexibility of the model provides low cost if scope and requirements are to be changed. Coming to the object-oriented approach, it us used because of its useful aspects like code reusability, flexibility, reliability.
riverloopsec / Banned H EmbeddedAn embedded-focused banned.h / strsafe variant intended to assist for Secure Software Development Lifecycle for Embedded Developers
edmond82 / Software Development Processes And MethodologiesSoftware Development Lifecycle Specialization
serverscom / DibctlSoftware for managing image lifecycle: build, test, upload and deprecation
