Software Development Example Project

[Jovanna Ponder]

SummaryA user story is an informal, general explanation of a software feature written from the perspective of the end user. Its purpose is to articulate how a software feature will provide value to the customer.

A key component of agile software development is putting people first, and a user story puts end users at the center of the conversation. These stories use non-technical language to provide context for the development team and their efforts. After reading a user story, the team knows why they are building, what they're building, and what value it creates.

The purpose of a user story is to articulate how a piece of work will deliver a particular value back to the customer. Note that "customers" don't have to be external end users in the traditional sense, they can also be internal customers or colleagues within your organization who depend on your team.

User stories are also the building blocks of larger agile frameworks like epics and initiatives. Epics are large work items broken down into a set of stories, and multiple epics comprise an initiative. These larger structures ensure that the day-to-day work of the development team (on stores) contributes to the organizational goals built into epics and initiatives.

For development teams new to agile, user stories sometimes seem like an added step. Why not just break the big project (the epic) into a series of steps and get on with it? But stories give the team important context and associate tasks with the value those tasks bring.

Another common step in this meeting is to score the stories based on their complexity or time to completion. Teams use t-shirt sizes, the Fibonacci sequence, or planning poker to make proper estimations. A story should be sized to complete in one sprint, so as the team specs each story, they make sure to break up stories that will go over that completion horizon.

This structure is not required, but it is helpful for defining done. When that persona can capture their desired value, then the story is complete. We encourage teams to define their own structure, and then to stick to it.

User stories describe the why and the what behind the day-to-day work of development team members, often expressed as persona + need + purpose. Understanding their role as the source of truth for what your team is delivering, but also why, is key to a smooth process.

Create UI extensions using HubSpot's sample projects to get familiar with what's possible when building CRM UI extensions. These sample projects can be used as inspiration, reference, or starting points for your own projects.

View a high-level summary of data from associated deals. Follow through the tutorial to add the project to your account, create two example deal records to display data from, then customize the extension with additional components.

Explore the various logger API methods by sending custom logs from deployed extensions. When used in local development mode, logs will be sent to the browser console. In cases where the extensions fail to load, a trace ID will be generated which you can then use to trace the log within the app's logs in HubSpot. Learn more about the custom logger API.

Example use case: a salesperson in your account makes frequent changes to a contact's properties and associated fields on a custom card and requires a seamless editing experience to avoid manual page refreshes.

What's included: a Refresh properties between custom card and CRM page card that displays the latest firstname and lastname property values when changed on the CRM record page, as well as a lifecycle stage dropdown menu that you can update on the card and immediately see the change reflected on the CRM record page.

Always follow your funding opportunity's instructions for application format. Although these applications demonstrate good grantsmanship, time has passed since these grant recipients applied. The samples may not reflect the latest format or rules. NIAID posts new samples periodically.

The text of these applications is copyrighted. Awardees provided express permission for NIAID to post these grant applications and summary statements for educational purposes. Awardees allow you to use the material (e.g., data, writing, graphics) they shared in these applications for nonprofit educational purposes only, provided the material remains unchanged and the principal investigators, awardee organizations, and NIH NIAID are credited.

Freedom of Information Act (FOIA). NIAID is strongly committed to protecting the integrity and confidentiality of the peer review process. When NIH responds to FOIA requests for grant applications and summary statements, the material will be subject to FOIA exemptions and include substantial redactions. NIH must protect all confidential commercial or financial information, reviewer comments and deliberations, and personal privacy information.

Note on Section 508 Conformance and Accessibility. We have reformatted these samples to improve accessibility for people with disabilities and users of assistive technology. If you have trouble accessing the content, please contact the NIAID Office of Knowledge and Educational Resources at dea...@niaid.nih.gov.

The Research Enhancement Award (R15) program supports small-scale research projects to expose students to research and strengthen the research environment at educational institutions that have not been major recipients of NIH support. They are awarded for up to 3 years.

The R21/R33 supports a two-phased award without a break in funding. It begins with the R21 phase for milestone-driven exploratory or feasibility studies with a possible transition to the R33 phase for expanded development. Transition to the second phase depends on several factors, including the achievement of negotiated milestones.

The SBIR (R43/R44) and STTR (R41/R42) programs support domestic small businesses to engage in research and development with the potential for commercialization. Read more about NIAID Small Business Programs.

*Dr. Mark Poritz submitted the original grant application. In the course of the first year of funding, Dr. Andrew Hemmert took on increasing responsibility for the work. For the grant renewal, Dr. Poritz proposed that Dr. Hemmert replace him as the PI.

The Research Scientist Development Award (K01) supports those with a research or health-professional doctoral degree and research development plans in epidemiology, computational modeling, or outcomes research. Read more about NIAID Research Career Development (K) Awards.

The Mentored Clinical Scientist Research Career Development Award (K08) supports those with current work in biomedical or behavioral research, including translational research, a clinical doctoral degree such as M.D., D.V.M., or O.D., and a professional license to practice in the United States. Read more about NIAID Research Career Development (K) Awards.

The Mentored Patient-Oriented Research Career Development Award (K23) supports those with a clinical doctoral degree, who have the potential to develop into productive, clinical investigators, and who have made a commitment to focus their research endeavors on patient-oriented research. Read more about NIAID Research Career Development (K) Awards.

The Extramural Associate Research Development Award (EARDA) (G11) provides funds to institutions eligible to participate in the NIH Extramural Associates Program for establishing or enhancing an office of sponsored research and for other research infrastructure needs. Search for NIAID G11 Opportunities.

The U01 research project cooperative agreement supports a discrete, specified, circumscribed project for investigators to perform in their areas of specific interest and competency. Learn more about NIAID Cooperative Agreements (U).

How does one go about developing project code from the examples provided by ST I.E. setting up a project with the correct includes, initialization of the BLE protocol, and successfully communicating between two BlueNRG devboards?

I am working with ST's BlueNRG-LP evaluation board (STEVAL-IDEB011V1) for a college project and I along with my other teammates are a little outside our depth with working with this particular board. Our project involves a basic transmission of data between three devices in a smart garden watering system application. A moisture sensor collects data on the moisture content of the soil and transmits it to a controller which will automate water flow when needed, while itself transmitting information to a BLE compatible cellphone with an app to display the data of the garden and offer controlling inputs (I.E. how the garden should be watered).

Progress has been made in coding to the devboard on a simple microcontroller level for the data collection portion of the project, neither myself nor my other team members have been able to make headway with the actual bluetooth side of the ball.

I have attempted to get the functionality through the BlueNRG GUI and use its "save as C-Code" functionality once I have everything initialized and my services defined, however this has not created any projects which are actually useable with WISE-Studio (leaving a host of errors which stem from something not being included correctly).

I have been unable to follow the methodology of the example code provided through the BlueNRG navigator program and have not been able to distinguish the segments of code which correspond to the specific example and that which is required for basic setup of the BLE protocol.

I still don't quite understand all the steps that are required to create a buildable project from the GUI, once the save as C-Code has been used and placed in the project\examples folder, how do you go about getting the required libraries in that folder?

Lack of employment opportunities for people with disabilities continues to be a significant problem, especially in rural communities. Self-employment and small business development often can be the only viable employment option for people with disabilities in rural areas, but these areas also often lack economic development support. The Rural Community Economic Development Project was developed to address employment issues of people with disabilities through rural economic development while exploring the leadership roles that people with disabilities and rehabilitation professionals might take in the process. Phase 1 of the project involved a community assessment of two rural areas of eastern Utah and northern Vermont.

3a8082e126