1 / 6

Creating Systems: 3 Things You Need

When it comes to managing complex projects, planning and organisation are key to effective communication of needs. And to really pull this off, startups need systems and processes in place. Read on, as Alliance Software discusses the top 3 things you need to create a system.

Download Presentation

Creating Systems: 3 Things You Need

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. I’m going to use curry ordering as the example to show you a working example through each of these scenarios: inputs, processing and outputs. This one is almost embarrassingly simple. I have two software engineering degrees because one wasn’t enough. One of the things they teach every software engineer is creating a system can be modeled using inputs, processing and outputs. The beauty of this approach is that it is really simple and clear and this is the approach I often find myself coming back to when I’m in the middle of something. I’m working with a customer and it feels really complex. We’re wrestling with things, let’s just step back and I say, what are the inputs, what is the processing and what are the outputs? Creating a system can be mapped this way. Let’s look at the inputs, processing and outputs for a curry ordering system. We have to input the menu into the curry ordering system, the menu changes. We have to put orders into it and we have to put in payment methods or payment preferences. We have to sum the orders, we have to add them up, we have to check that the delivery value is met. You can’t put a curry order through for less than $30 with our local curry shop, otherwise

  2. someone has to drive down and pick it up and we store IOUs we do some processing. Outputs, we get reminders. Our system tells people it’s time to order curry, 10 o’clock every Friday. You get reminded, go and order your curry. It puts out an order summary, it tells us what we’ve got and who owes us the money. It does the debt collection summary. So we need a system to output our orders. Inputs are typically data from people or systems. So it’s data that people are going to put into it and it’s data that comes from other systems. Increasingly it’s data from other systems. When you’re thinking about inputs, think about that. The outputs are screens and paper, that’s what is going to come out of your system. If you go to your developer and say these are my inputs, this is the processing and these are the outputs, you will have communicated better than most clients do. This is a pretty simple, straight up technique, number one.

  3. IN THIS VIDEO: Ben Stickland, the founder of Alliance Software, talks about inputs, processing, outputs, and why these three things are important in creating systems.

  4. You, too, can become well-versed in creating systems. Explore our full range of services to find out how we can help.

More Related