ACS & DAMA Joint Professional Development event
Event Start:
Tue 21 Nov 05:00 PM AEDT
Event Finish:
Tue 21 Nov 07:30 PM AEDT
Registration End Date: Tue 21 Nov 02:00 PM
<i>Registration from 5:00 pm, Presentation at 5:30 pm, Networking canapes and drinks from 6:30 pm.</i><br><br>Emily has been made the “subject matter expert” for an IT project. Her job is to specify the business requirements for the new system. Emily knows her part of the business well and she can see that there are some inefficiencies in the way the team does things now. The system is a set of screens for data-recording, and isn’t oriented towards stepping through a transaction from beginning to end. In fact, there is no clear delineation between transactions.<br><br>Emily hasn’t been closely involved in an IT project before. She feels intimidated by the IT dudes who say “tell us your requirements”, and by their talk of “functional specifications” and “user stories”. She doesn't understand all their talk about object orientation, unified modelling, data driven, etc. She feels inadequate for not understanding what they are talking about and what they expect from her.<br><br>The business analysts confuse her even more by showing her their previous work – one showed her a document that listed requirement after requirement for a hundred pages and more. Others showed her their one-sentence user stories that they said the IT guys could develop a system function from. User stories seemed like easy work for her, but Emily is awestruck by the magic that was promised by this new “agile” approach.<br><br>Emily can't understand how the IT analysts and developers could ever hope to develop a coherent system that could meet all these individual requirements in a joined-up way. There seemed to be an unspoken assumption that a new system that supported a better way of doing business would emerge, as if by magic. After all, an improved business operation – not just a new system – is the point of this investment, isn't it?<br><br>Emily needs a structure to think about her business needs in a different way. It strikes her that most of the processes are actually quite similar, it is only the content (the data, workflow, the output) that varies. <br><br>When a customer chooses to use a service that Emily’s business offers, they first submit a request, just like a shopping order, or an application for a permit. This customer request is an event that the business must deal with and provide a response back to the customer – fulfilment of the order, or a decision on the permit. Businesses exist to process such events, no matter what kind of business it is. <br><br>Emily thinks that an approach structured around a straight-forward pattern like this might simplify her task of specifying the business requirements. Looking at each task in turn, she could focus more on the business workflows, data needs and business rules, and less on system functionality and screens. She would be able to retain a holistic view of how the business could work more smoothly, processing its transactions like a clock ticking over the minutes from one state to another.<br><br>But could the IT team consume her new way of specifying requirements? Would her small rebellion succeed?
To share the Knowledge with members
Event Terms and Conditions
Disclaimer
COVID-19 Event Attendance Compliance
By registering to attend an ACS in person event you are agreeing to the below terms and conditions
Personal information collection notice
By registering for this event, you are providing personal information to the Australian Computer Society. In accordance with the ACS Privacy Policy, ACS collects personal information through registrations and attendances at its events for the purposes of:
If the required information is not provided, we or any involved third parties, may not be able to respond to you, update you, or provide appropriate services or events to you.
We may obtain personal information directly from you or from someone who registers for the event on your behalf. If you provide us with personal information about another person, you must do so only with their consent and agree to make them aware of this privacy notice.
ACS may share your personal information with third parties for the collection purposes noted above or as set out in our Privacy Policy, where it is reasonably necessary for, or directly related to, one or more of our activities, or required by law.
When you register to participate in an overseas event, we may send personal information we collect overseas.
See our Privacy Policy at https://www.acs.org.au/privacy-policy.html for more information about our privacy practices.
![ACS MSA Portal - Agent Onboarding Session [VIRTUAL]](/content/dam/acs/ACSimages/events/events-default-image-240x160.png)